[NTLUG:Discuss] Java - Firefox Plugin

terry trryhend at gmail.com
Thu Nov 27 09:32:05 CST 2008


Update:
I went over there on Monday afternoon and found that I had actually fixed it
without realizing it.  I had placed the symbolic link for the
libjavaplugin_oji.so file in the /usr/lib/mozilla/plugins directory, (which
does, in fact, make it perminate), but I also had placed an additional
symbolic link for the libjavaplugin_oji.so file in the
/usr/lib/firefox-2.0.0.18/plugins/ directory, (which wouldn't hurt anything,
but  is just a redundancy, and so I removed it).

Conclusion(s):
The directions were correct for this particular detail on
http://fedorasolved.org/browser-solutions/java-i386  There were other
details that don't seem necessary and they confused the issue - (and I'm not
sure what some of the rest of it was all about, like creating the java.sh
script and "--config java" ... but those are unrelated issues).

The confusion comes from the Mozilla browser evolutionary name change(s).
 What we had in the past was two browsers from the same line and we were
installing plugins for them both.  The default procedure was to install to
Mozilla's plugin directory, but you had to to specify other browser plugin
directories to place the file into so that your other browsers would be able
to use the same plugin.  At that time, we did, in fact, need to place the
plugin in two different places in order for Mozilla and Firefox to both use
the same plugin.  But now, Mozilla has changed  to SeaMonkey.

What we see today is that Mozilla has changed to Seamonkey but yet the
/usr/lib/mozilla/plugins directory is still part of our directory structure
- which is a good thing because [I see now] that we can use it to save the
plugin and make it static so that browser upgrades won't loose it anymore.
It's a clever solution, but the name  "mozilla" is what was throwing us off,
[.... well some of us anyway,  others may be reading this that knew all
along and just didn't know exactly how to explain it to us].  But  there is
definitely some confusion, we have  been installing the JRE plugin in a
number of different ways

Tony's solution to "create the symlink in the users home directory:
$HOME/.mozilla/plugins" is probably a good one  too - I'm sure it works just
fine.

Someone will probably change the way this works again - the recommended
method - my only hope is that next time it will be a bit more
user-understandable.

Thanks again for all the good comments / suggestions.


More information about the Discuss mailing list