[kepler-dev] [Bug 3949] - Get the installer working with the new build system

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3949





------- Comment #2 from berkley at nceas.ucsb.edu  2009-04-20 15:37 -------
Have run into all kinds of problems trying to make a Windows EXE file with our
new module setup.  Launch4J assumes that all of the code is in one jar file and
builds an executable around that.  I've automated the creation of the manifest
file in the loader.jar file so that it includes all of the other kepler jar
files.  This mostly works, except that then all paths are relative to wherever
you've issued the java -jar command, no matter where the loader.jar file
actually is.  This causes all sorts of problems with the way we're finding
configs and the way that the MoMLParser wants to find the configs for the
-kepler argument.  I'm mostly going to punt on this for now, but will try to
revisit it later.  Spent three days on this with mostly nothing to show.  I'll
move on to creating the OSX .app directory, which should be much easier.  Then
we'll at least have a launcher for each os, even if the windows one is a .bat
file for now.