Closed
Bug 685116
Opened 13 years ago
Closed 12 years ago
plugin.scan.SunJRE value has no effect
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: clockgraveyard, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 5.2; rv:6.0.2) Gecko/20110902 Firefox/6.0.2 SeaMonkey/2.3.3 Build ID: 20110902180055 Steps to reproduce: For testing purposes, I would like SeaMonkey to use the Java 5.0 plugin and JRE (not just the JRE). Prior to SeaMonkey 2.3, I would just copy the Java 5.0 np*.dll files to the SeaMonkey plugins directory. SeaMonkey 2.3, however, discovered my Java 6 JRE and used that. Following the advice at http://kb.mozillazine.org/Plugin_scanning, I tried to prevent the scan for JRE 6 by setting the config value plugin.scan.SunJRE to 1.9. Actual results: Nothing changed Expected results: I had hoped that the automatic scan would have been unsuccessful and that only the explicitly copied DLLs in the plugins directory would be used.
Updated•13 years ago
|
Component: General → Plug-ins
Product: SeaMonkey → Core
QA Contact: general → plugins
Version: SeaMonkey 2.3 Branch → 6 Branch
Comment 1•13 years ago
|
||
The old npoji plugin doesn't work anymore. JRE1.6 U14 or later is required and it comes with the new java plugin npjp2.dll.
Comment 2•13 years ago
|
||
With the new add-ons manager, it has become quite easy to enable/disable plugins individually. In particular if you have two different plugins installed for a common functionality, you can choose which one to use. Of course, if only one is up-to-date you should disable the other.
Reporter | ||
Comment 3•13 years ago
|
||
Thanks, Tony and Matthias. I thought I'd seen the JRE 5.0 plug-in work when I uninstalled JRE 6, but I must have been deluding myself. I think my best bet is to keep a SeaMonkey 2.2 installation around for when I want to use the JRE 5.0 plug-in.
Comment 4•12 years ago
|
||
(In reply to clockgraveyard from comment #0) > For testing purposes, I would like SeaMonkey to use the Java 5.0 plugin and Not supported anymore. R.Invalid. > I tried to prevent the scan for > JRE 6 by setting the config value plugin.scan.SunJRE to 1.9. That part might be bug 583566.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Comment 5•12 years ago
|
||
(In reply to Serge Gautherie (:sgautherie) from comment #4) > > I tried to prevent the scan for > > JRE 6 by setting the config value plugin.scan.SunJRE to 1.9. > > That part might be bug 583566. Or bug 358090.
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•