[kepler-dev] [Bug 2319] - Ptolemy build problems

[bugzilla-daemon@ecoinformatics.org]

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

jones at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From jones at nceas.ucsb.edu  2005-12-16 08:56 -------
The current Kepler installers don't use ptolemy.jar.  Instead, the build process
under the "run" target builds a "kepler.jar" that contains all of the classes
from ptolemy and the classes from Kepler.  We do this specifically so that we
can control the placement of the "exp" files in the resulting jar file (as they
override corresponding classes in ptolemy.jar).

Our initial builds did in fact use ptolemy.jar, but we ran into consistency
problems on different platforms and JVMs when loading the exp classes.  So we
switched to the approach of building a consolidated kepler.jar file.  But this
file takes quite a while to build, so the "run-dev" target was also created to
run directly from build/classes in order to speed up the edit-compile-test
cycle.  This "run-dev" target is only intended to be used by developers, and is
not ultimately how kepler is shipped.  So your suggestion to use ptolemy.jar
will not work without some significant changes to our build process.

I would like to eliminate this distinction between the two targets (run and
run-dev). I would also like to go back to using ptolemy.jar.  But that requires
resolving our issues with inconsistent classloading for the exp directory.  One
approach would be to eliminate the exp directory alltogether, which would also
be good.  However, we clearly need a place to experiment with changes to the
ptolemy tree before checking them into ptolemy.  I'm not sure the ptolemy group
wants all of the changes that we have made in the exp tree. We should, however,
be better about merging our code in exp regularly into the ptolemy tree.  I will
enter a separate bug for this task.