Closed Bug 149820 Opened 23 years ago Closed 21 years ago

MRJ Plugin Info Mania

Categories

(www.mozilla.org :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: tommybee99, Assigned: endico)

References

()

Details

As of right now there are at least three MRJ Plugin web sites: http://www.mozilla.org/oji/MRJPlugin.html hasn't been updated since 2000, makes no mention of OS X plugin http://homepage.mac.com/pcbeard/MRJPlugin/ contains links to the latest plugin version http://homepage.mac.com/mrjplugin/ states "This is NOT an official page!" but uses Mozilla site style and contains "Copyright © 1998-2001 The Mozilla Organization." at the bottom. I think it would make sense to at the very least have the latest MRJ Plugin information available at mozilla.org -- I got the impression (perhaps from VersionTracker.com?) that some users thought that because the latest plugins are on Mac.com rather than mozilla.org the plugins are an outside project. The third site probably doesn't matter as much since it does mention that it is an unofficial site, but I could see having that site out there leading to some confusion.
The official site for the MRJ OJI plugins should be reduced to just two: http://www.mozilla.org/oji/MRJPlugin.html and http://www.mozilla.org/oji/MRJPluginCarbon.html I have no control over http://homepage.mac.com/mrjplugin/ At one time I believe tnoyes@mac.com was posting plugins there.
changed page to point to Patrick's. Patrick, do you want that address?
Blocks: 120459
I'm not sure about ftp://ftp.mozilla.org/pub/OJI/MRJPlugin.sit.hqx is this file always updated?
OS: Mac System 9.x → MacOS X
QA Contact: imajes → stolenclover
MRJ download is only required for Netscape 4.x, this page is obsolete -> wontfix For Java information, users should refer to the release notes.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.