If one installs package icedtea-web, the man file icedtea-web-plugin.1 comes with it, and it references a file named "IcedTeaPlugin.so" without stating location; unfortunately IcedTeaPlugin.so does not arrive with it :-) Given that Oracle is eliminating the plugin with Java 9, I'd really love to be running IcedTea/OpenJDK instead of Oracle-Sun if possible.
So I investigated this issue a little bit.
In https://git.solus-project.com/packages/icedtea-web/tree/package.yml I noticed the following: %configure --disable-plugin --with-jdk-home=$javadir --with-jre-home=$javadir/jre/
Inclusion of the --disable-plugin argument results in IcedTeaPlugin.so not being "installed". If I remove --disable-plugin build fails with the following error:
configure: error: Package requirements (mozilla-plugin) were not met: No package 'mozilla-plugin' found
I guess this is because npapi-sdk is not listed in dependencies. I have peeked into the Archlinux PKGBUILD of the IcedTea-Web package (https://www.archlinux.org/packages/extra/x86_64/icedtea-web/) and it has npapi-sdk in dependencies.
Upstream URL of npapi-sdk is https://bitbucket.org/mgorny/npapi-sdk. Before removing --disable-plugin in https://git.solus-project.com/packages/icedtea-web/tree/package.yml npapi-sdk must be present in the system and then it should be included in dependencies.
Packager of this thing here.
If I remember correctly, decision was to not include npapi because it's removed or soon to be removed form recent browser (aka: chrome, firefox)
You can download and launch the .jlnp files.
Didn't mention that it could be cool to have the plugin working
This is unfortunate, because some web apps (corporate banking in my case) use Java web plugins. I don't like using Java plugins, but I need it to get the job done. Would be nice if users had opportunity to choose if they need web plugin functionality or not themselves.
Would be nice if users had opportunity to choose if they need web plugin functionality or not themselves.
Not sure to understand what you mean here. This is not closed discussion, the plugin can be include, I guess. Need to figure out if it's compliant with Solus guidelines regarding old, not maintained software, and if it's doable.
Plus did you try to open .jpnl files. It still opens things in your web browser.
Given NPAPI support in Firefox is only enabled upstream for a select amount of items, with the rest going to WebExtensions, and us not having any intention to support 52.0 ESR, closing as wontfix.