[kepler-dev] [Bug 4091] - Make it so the build system can use a "blessed" version of Ptolemy.

[bugzilla-daemon at ecoinformatics.org]

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





------- Comment #5 from cxh at eecs.berkeley.edu  2009-05-27 11:11 -------
Ok, good news that I can build against the ptII head.

The word "update" in "ant update" means something specific, which is that
"svn update" is being run.  I think that by changing the meaning of update,
which means that "ant update" is not building against the head is a misuse
of the word "update", but it is not that serious.  I think "ant update-stable"
should update against stable versions of all the repositories, including
kepler.  "ant update" should update against the head of all the trees.

That is just my $0.02, do as you wish here.

Happily, when ant update is run, the message shows that the head of Ptolemy is
not being retrieved:

[update-modules] Updating ptolemy...
[update-modules] svn -r 53941 update /Users/cxh/src/kepler/ptolemy 
[update-modules] At revision 53941.

The above message should be modified to be very clear when I'm running against
a version of Ptolemy that is not the head and how to build against the head by
running the ant commands you describe.  

Where is the documentation of the procedure for how the stable of version
number of Ptolemy is determined?  For example, how often is the version
of Ptolemy checked?  How is it updated?

The next step is to definitely include a smoke test that starts up Kepler to
validate the configuration.  This will catch many errors.  Ptolemy has
this capability available in the about:copyright facility.  Basically, if
you go the the "information about Ptolemy" link and follow the copyright page
eventually there is a list of configurations and tests.  

Kepler could run the same tests by getting the configuration and calling
ptolemy.actor.gui.Configuration.check().