2855 - Need to handle non-installable .JAR's better

Status: VERIFIED INVALID

(Core Graveyard :: Installer: XPInstall Engine, defect, P1)

Description

[John Giannandrea]

(This bug imported from BugSplat, Netscape's internal bugsystem.  It
was known there as bug #62432
http://scopus.netscape.com/bugsplat/show_bug.cgi?id=62432
Imported into Bugzilla on 02/03/99 10:47)

If you click on a .jar file and its not an ASD file you get a
dialog that says:

SmartUpdate failed: JAR archive is missing an installer file %s.

Since there will be many more jar files in the world than ASD installers
(signed scripts, most java programs) users will come across these files
frequently and this is a confusing user message.

Bug #59454 (making the Windows association for JAR files be Navigator
by default depends on this being fixed).

-jg

Comment 1

[Aleksandar Totic]

I'll change the wording to anything you'd like, just give me the text.
In the future, we'll be smarter about this.

Comment 2

[John Giannandrea]

Scott can come up with good English...

Comment 3

[sk]

Per Aleks request, this goes back to jg. Aleks doesn't think the change
will be allowed. Below are my wording suggestions:

A similar dialog in Navigator says: "Unable to launch application. The
application was not found."

So, this dialog might read: "Smart Update unable to launch Java file. A
necessary component was not found."

If more appropriate, you could swap some other text for 'Java file' or
'necessary component'. For example, an alternative might be "SmartUpdate unable
to launch file. The file's type was not recognized."

Comment 4

[John Giannandrea]

Aleks, if you want to later this bug thats up to you, but you know
that I think its just wrong to ship soemthing this broken.
But assigning the bug to me just because you dont care enough to argue
for it is ludicrous.  Its not my bug, I didnt create it!
-jg

Comment 5

[Sean Su]

I'm adding myself to the cc: list.

Comment 6

[ko]

4.0 Windows has shipped. Verified LATER.

Comment 7

[Daniel Veditz [:dveditz]]

We need to deal with non-SmartUpdate .JAR's better. New MIME type and
extension? Re-think the issue for 5.0

Comment 8

[Daniel Veditz [:dveditz]]

Oops, not a "5.0 SF1" stopper

Comment 9

[leger]

Moving all Bugsplat bugs for 5.0 to Bugzilla.  dveditz, do you still want this
moved over for a reminder, or can I close this bug?

Comment 10

[Daniel Veditz [:dveditz]]

Please carry this one over to 5.0

Comment 11

[Daniel Veditz [:dveditz]]

We are going to use a new MIME type and extension (.xpi -- "zippy") in 5.0 so
this 4.x Communicator bug is no longer relevant

Comment 12

[Jimmy Lee]

Verifying per Dan's comments.  Two years later, and this is addressed.  Amazing.

Comment 13

[leger]

Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine

Comment 14

[Jesse Ruderman]

*** Bug 2856 has been marked as a duplicate of this bug. ***