Operating System: All
This issue is for the download for Milestone 3:
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
Amy did the work to create installer and gets to work on the bug too.
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.
Also, unjar is necessary to display license file before installation since we
removed click through.
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.
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 ?
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.
Changing it to RFE per discussion with Jerome.