Thanks

The idea was to be able to pull automated installation scripts (generated by the finish panel) from multiple locations when executing the AutomatedInstaller. Currently when the AutomatedInstaller runs, it will only attempt to load the XML installation script file from a file. We had a need to load the installation script from the class path so that it could be bundled inside the installer jar file.

Basically the idea was to create a "Universal Installer:" similar to the one used by Oracle, except that it would be automated. This requires the use of multiple install scripts for multiple applications/versions.

Example:

Creating a single jar to update multiple applications A,B, C, D, is easy using the pack selection mechanism, but previously it also required distributing multiple files:

the installer.jar
A.auto.xml
B.auto.xml
C.auto.xml
D.auto.xml
...etc.

The LocalInstallScriptLocator allows loading install scripts from the class path so that now instead of distributing multiple files, we can bundle all of the installation scripts inside of the installer jar and just distribute the jar file. This makes it much easier on the end-technician (or end-user).

This will not change any existing IZPack behaviour since it will still attempt to load from the file first and only check inside the jar file if the file does not exist.

I would also like to add functionality for downloading installation scripts via HTTP and FTP, but I wanted to know what API (commons http client, java.net, etc. ) you prefer for doing so.

Thanks,

Chris

Ok for inclusion, but I would need:

1. that you add a license notice at the top of new files (we have templates in the src/ folder of IzPack)
2. documentation text for end-users (plain text will do if you don't want to patch the documentation which is using docutils.sf.net).

Thanks!