As usual, I wasn't quite clear enough :-)
The idea is to use the revision number of the last pluto change included in the jar. Then, anyone can reproduce the jar contents by checking out that pluto revision and building. My pluto archive indicates 164158 as the last revision, so I'd use that. (I recently realized that svn up reports "at version xxx" where xxx is the last commit at apache, not the project you are updating)
thanks david jencks
On May 17, 2005, at 6:23 AM, David Sean Taylor wrote:
David Jencks wrote:Since pluto is using svn, you might want to use the svn revision number as the version number.That makes sense.
pluto-PRIVATE-12345678.jar
would leave no doubt about the provenance and contents of the jar and let anyone reproduce it at will by checking out that revision.
Which file's revision number do you recommend, since the jar is not checked into SVN?
-- David Sean Taylor Bluesunrise Software [EMAIL PROTECTED] [office] +01 707 773-4646 [mobile] +01 707 529 9194
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
