Mozilla based products will first attempt to load plugins from the ~/.mozilla/plugins directory before loading from /usr/lib[32|64]nsbrowser/plugins. This allows a user to overload the system javaplugin and therefore have control over which vm they use. At the moment the java-nsplugin.eselect module only allows for setting of a system wide plugin.
Created attachment 97736 [details, diff]
add support for users adding java plugins to their home mozilla plugin directory
Firstly I consider this patch to be for proof of concept only, yet I believe that technically the methods I have used are sound.
This patch adds the following functionality to the java-nsplugin.
The ability to add javaplugin.so to ~/.mozilla/plugins/ on x86 arch
and on multilib systems (amd64) the ability to add BOTH javaplugin-32.so and javaplugin-64.so.
javaplugin-32.so uses the emul-linux java libraries to provide 32bit plugin support. as both 32 and 64 bit plugins can reside in this directory together all mozilla products will have to be tested to ensure they do not fail attempting to load the wrong library (I dont forsee this to be an issue).
As x86 has the possiblility of having a greater range of different system/user plugin possibilities I would like this arch to be tested heavily to ensure that mozilla products don't attempt to load both user and system java plugins
*** Bug 139906 has been marked as a duplicate of this bug. ***
I know I tried this before (I already told you on IRC) and about:plugins then reported both user and system plugin. But apparently that's not a problem, see http://www.javatester.org/version.html method 4.
Created attachment 98332 [details, diff]
patch to add user level nsplugin support to eselect
This just finishes the work of the previous patch
java-nsplugin has been removed as of 0.2.0. Only Oracle's plugin and icedtea-web are of concern now. I was going to install them under nsbrowser/plugins simultaneously, leaving selection to the browser, but Firefox only allows you to disable all Java plugins together, not individually. Choosing between them is now therefore down to only applying the nsplugin USE flag where appropriate. This is satisfactory now that plugins have been all but outlawed.