Closed Bug 2855 Opened 28 years ago Closed 26 years ago

Need to handle non-installable .JAR's better

Categories

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

All
Windows NT

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: jg, Assigned: dveditz)

References

Details

(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
I'll change the wording to anything you'd like, just give me the text. In the future, we'll be smarter about this.
Scott can come up with good English...
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."
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
I'm adding myself to the cc: list.
4.0 Windows has shipped. Verified LATER.
We need to deal with non-SmartUpdate .JAR's better. New MIME type and extension? Re-think the issue for 5.0
Oops, not a "5.0 SF1" stopper
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?
Please carry this one over to 5.0
Status: NEW → ASSIGNED
Component: Composer → XPInstall
Product: MozillaClassic → Browser
QA Contact: 4138
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
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
Status: RESOLVED → VERIFIED
Verifying per Dan's comments. Two years later, and this is addressed. Amazing.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
*** Bug 2856 has been marked as a duplicate of this bug. ***
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.