96251 - Mozilla/N6 trunk build going to ftp.netscape.com/...6.0..site for Java

Status: VERIFIED DUPLICATE of bug 202952

(Core Graveyard :: Plug-ins, defect)

Description

[Grace Bush]

NOt sure if these bits differ - both seem to run without problems
Steps to reproduce:
1. Download  both N6 trunk build and Mozilla build for 2001082106
2. Install recommended setup type (N6) and complete setup type for Mozilla
3. go to http://www.java.sun.com
4. At warning that you need a plugin, choose Linux plugin for Java

expected results:  plugin would be downloaded from most recent bits (sixe 13262 
placed 8/1/2001)
actual results: going to   6.0 download directory and getting bits (size 15151,
placed 7/25/2001)

Comment 1

[Daniel (Leaf) Nunes]

i'm not sure how the default plugin urls are determined, but i'm sure av does ;)

Comment 2

[cls]

After clicking "OK" on the plugin dialog, a new window opens 
http://home.netscape.com/plugins/jvm.html .  I'm pretty sure that's the page
that needs to be updated.  And since that's not even close to being a build
config issue, I'm punting this to Browser-General.

Comment 3

[av (gone)]

This URL has been hardcoded in the default plugin itself by, I believe, OJI 
people. Adding edburns.

Comment 4

[Asa Dotzler [:asa]]

->OJI

Comment 5

[Denis Antrushin]

OJI people hardcoded that URL because, I think, netscape plugin finder
(http://cgi.netscape.com/cgi-bin/plug-in_finder.cgi) fails to find plugin
for java.
We can't do anything here until plugin finder will find java plugin.

Moreover,http://home.netscape.com/plugins/jvm.html now points to java 1.3.1_02
(ns 6.2.2 bits).
Back to Browser-General for closing or fixing plugin finder

Comment 6

[av (gone)]

Arun, you are probably the best man to find right owner for this bug.

Comment 7

[Grace Bush]

Mozilla and N6 builds are now going to the 6.2.2 site for JRE and getting the 
proper version 1.3.1_02 via the 'get the plugin icon'

Comment 8

[Denis Antrushin]

removing myself from cc:

Comment 9

[Andreas Kunz]

Erm... this bug needs either a severe update or to be closed...

Comment 10

[Vidar Haarr (not reading bugmail)]

This is most likely a dupe of bug 202952. If you disagree, please reopen.
It could also be that this bug depends on 202952 - I'm not sure.

*** This bug has been marked as a duplicate of 202952 ***

Comment 11

[Michael Hendy (Hendikins)]

Smells like a dupe to me. v.