Multiple install typesIt is possible to deliver different install types in the same Jar. There must be a default install type that uses
or for a command line install
When launching from a scripted install (not a self-extracting Jar) the launch scripts will probably need to be modified to handle the new parameters correctly and to inform the user if an invalid -type has been specified. If not the installer will print a stack trace reporting that it can not find the config file.
Alternative configs are not validated during the ant task that creates the installer so they should be validated manually.
If creating different install types you will have to inform users that the options exist as they are currently only selectable on the command line. A GUI to this feature will probably not be implemented since it is possible to use the ifProperty attribute to achieve the same results and embed the alternative Ant tasks in the same build.xml file.