Issue Details (XML | Word | Printable)

Key: GLASSFISH-28
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Won't Fix
Priority: Critical Critical
Assignee: Amy Roh
Reporter: inder
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

downloaded jar should be double-clickable to run

Created: 31/Aug/05 11:50 AM   Updated: 21/Apr/11 04:53 PM   Resolved: 21/Apr/11 04:53 PM
Component/s: other
Affects Version/s: 9.0pe
Fix Version/s: 9.0pe

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: All


Issuezilla Id: 28
Tags:
Participants: Amy Roh, dochez, inder and kumara


 Description  « Hide

This issue is for the download for Milestone 3:
https://glassfish.dev.java.net/downloads/24Aug05_SCF.html

The downloaded file should be installable just by double clicking on it. Why do
I have to use command line to not just unjar the file, but also run the setup
script?



kumara added a comment - 21/Sep/05 10:17 PM

Amy did the work to create installer and gets to work on the bug too.


Amy Roh added a comment - 22/Sep/05 02:45 PM

Setup script is needed for appserver initial setup.

Paths used are specific to the local env like JAVA_HOME to create configuration
files by replacing tokens to create your appserver installation and domain.


Amy Roh added a comment - 22/Sep/05 03:16 PM

Also, unjar is necessary to display license file before installation since we
removed click through.


inder added a comment - 22/Sep/05 03:23 PM

Why cant the double-clicking of the jar itself run ant on the setup.xml script? Is there an alternate way to
look for JAVA_HOME property? Can we do without the JAVA_HOME env variable? As far as I know, previous
versions of the app-server did not require JAVA_HOME.

You can also look at some of the pre-defined system properties to better understand where java is
available, or assume that java is already in the path.


dochez added a comment - 12/Dec/05 01:40 PM

We don't need JAVA_HOME when dealing with double clicking since associations
should have been made by the native operating system to invoke the java -jar
command on the jar file. However that does not solve the issue that we need to
have the -Xmx256m paramater to be used for the unjarring to work properly.

So to fix this bug, we would really need to fix the -Xmx256m requirements, no ?


Amy Roh added a comment - 12/Dec/05 04:49 PM

The installer builder still requires -Xmx256m. Kohsuke recently put the project
out at https://poormans-installer.dev.java.net for us to fix its limitation, etc.


Amy Roh added a comment - 06/Mar/06 10:53 AM

Changing it to RFE per discussion with Jerome.