----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 21, 2001 2:20 PM
Subject: Re: [gump][cactus] problems with nightly zips
>
> Oh - and the Gump-produced output .jar and/or zip/tar.gz files are
supposed
> to be named 'blah-gump'. I believe Sam sets a default 'version' property
> to be -gump, to hopefully override the version property that many projects
> use. This way end-users won't get confused if they report problems
between
> an officially project-produced release build and some random nightly Gump
> build.
Several things here :
1/ I don't like that convention because it messes up all tools that you use.
Ok, emacs user would not have problems, but when you use IDEs or any other
tools (even Ant build files) you'll need to change all your properties that
refer to the jar and then change them back for releases ... I much prefer
the jars be called by the normal names and have a manifest set correctly ...
:) [GUMP could modify the manifest if need be]
2/ You need to be consistent. Only Log4j is renamed to log4j-gump for Cactus
but there are 4 jars : junit, httpclient and cactus-ant
The more you describe the intent of GUMP the more I think I can only use it
as a dependency checker and not for night builds. The night builds are for
the project and should be to the project liking. Otherwise, they should be
copied to a gump nightly build directory only and not to the project one.
What do you think ?
-Vincent
>
> - Shane
>
>
> ---------------------------------------------------------------------
> 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]
