----- Original Message -----
From: "Sam Ruby" <[EMAIL PROTECTED]>
To: "Vincent Massol" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, April 04, 2001 12:04 AM
Subject: Re: Repost: [Cactus] What remains to do ...


> Vincent Massol wrote:
> >
> > Sam, after I make the move tonight (for me that is GMT+1) to commons,
> would
> > you be able to update the GUMP script to point to that location ? Would
> you
> > be able to also copy the generated files to a nightly deliverables area.
> You
> > can use the 'dist' target of Cactus to do that and set the 'dist.dir'
> > property prior to calling the Ant build script. The only issue that I
see
> is
> > with the names of the nignhlty deliverables. For the moment, the names
> that
> > the dist target makes end with the version number (that was for
> SourceForge,
> > I had to upload unique file names so I put the version number in them).
I
> > can either remove the version and then it will be up to GUMP to rename
> the
> > file with the date for exemple or I can change the dist target to do
that
> > and when we release a version we just manually copy the files from a
> nightly
> > build to the release area, renaming the files in the same process. What
> do
> > you prefer ?
>
> I'll take a look and see what I can do (I'm at ApacheCon, so don't be
> surprised if I miss a day or two)...
>

don't worry, it can wait a few days ... :)
Have fun !

> The thing I need to look at is the need to support two servlet APIs.
>

Why not ? Lots of persons use Servlet API 2.2 and it would be good to ensure
that it works all the time : imagine that JUnit changes an interface, then
cactus jar for Servlet API 2.2 will not work anymore.

> - Sam Ruby
>
> P.S.  My preference is for stable file names.  If you want to put the
> version number into either the directory or the jar name, I would suggest
> making the version number an Ant property.
>

My proposition for the file names is :

a) add version number for releases only. Ex: cactus-22-1.0.jar,
cactus-src-1.0.zip, ...
b) for every nightly build, create a directory named after the date (ex:
2001-04-04). Put the files into that directory with no version information.
Ex: cactus-22.jar, cactus-src.zip, ...
c) a release is done by manually copying the files in a given snapshot
directory to the release area (by the way, what will be the location for
releases ?).

Question 1 : who creates the snapshot directories and copies the generated
files into them ? GUMP ? Or my build.xml file ? I'd prefer it to be GUMP as
snapshots seem to be more it's responsibility. Tell me what you think

Thanks a lot.
Vincent

Reply via email to