On 23 Aug 06, at 3:32 PM 23 Aug 06, Wendy Smoak wrote:
On 8/23/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
If you are building with m2 there is no reason for the metadata not
to be there. If the release plugin was used then the metadata would
be there. How was this release made?
Shale and Struts both use a 'test build' stage where we tag and build
a distribution, then vote on it later.
We 'mvn deploy' to the snapshot repository, then vote on the release,
and then make a valiant attempt to get everything Maven needs moved
over to the ibiblio rsync repository.
I think here you could just use the release plugin instead of the
deploy. You would release:prepare to tag a release and then
release:perform to build and deploy it. If you do this to a staging
area you can still vote on it and move it somewhere else later but
the metadata will be there.
With Carlos' help, the best I've come up with is documented here:
* http://wiki.wsmoak.net/cgi-bin/wiki.pl?Struts135ReleaseDiary
I'll have to dig up a couple of threads on repository@ and a recent
one here where Brett suggests that this 'build promotion' problem
could possibly be addressed in Archiva.
If these are releases then you can still use the release plugin
because you want the release info. Achiva could then help to move an
approved release from the staging area to the repository that's
sync'd . I think basically all you need to do is use the release plugin.
Thanks,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Jason van Zyl
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
