[Triplea-develop] installer

[Adam <axi...@em...>]

I just committed an installer process in the source tree. I think it is okay to put it in right now because it does not affect any source, just the build process.

The installer works as an ant task, "installer" and also "win-installer". installer should work on non-windows platforms, and creates a jar file that you could run with "java -jar triplea-install.jar". This should then extract all of the goodies in a pleasant way to a specified directory. I did not do any extra configuration for mac/x windows setups as of now, so it is windows centric, though it should work on them in limited capacity. The win-installer ant task creates an executable from the jar file, so all a windows user needs to download is the .exe file. The packaging of everything is done by a program called izpack. The creation of the executable is done by a program called jsmooth, but only works on windows because there are executables contained within the jsmooth ant process. 

JSmooth is supposed to check for java versions and whatnot, but I find that it doesn't work too well. It will detect whether or not java is on a system, but doesn't seem to be very developed in finding version numbers. Therefore, it should work great for those who do not have java or have java 1.5, but doesn't seem to run for those who have less than that java version number. The program MAY detect those with java under 1.5, but on the two machines I have access to that do not it simply throws up an error message and does not run.

All files for these programs should be contained within the source tree at this point, standalone jar's and configuration files. The installation files are contained in installer/*, and the final output is in release/TripleA-Installer.exe.

If anyone has problems running this, please let me know so I can fix it. 

I am taking a look at the uninstaller now for ease of use. Right now no registry changes for extensions are done, as I have not been able to find a solution. Right now triplea doesn't accept filenames as command line arguments so it shouldn't be an immediate issue.

Adam