Peter Donald wrote:
the commands are right here:
http://wiki.apache.org/excalibur/ReleaseManagement
http://wiki.apache.org/avalon/AvalonReleaseManagerHowto
Egads. Some of this is not good. You can not reproduce a build from a
tag which kinda defeats the purpose of a tag IMHO. Each separate
component is not independent as they reference things outside their
build hierarchy (even if it is just the parent project file). My
suggestions is when you tag that you copy the entire trunk into tags
directory. Something like
svn copy \
https://svn.apache.org/repos/asf/excalibur/trunk
https://svn.apache.org/repos/asf/excalibur/tags/MyComponent-Version-Release
+1 - this would ensure total consistency of the snapshot of the repo:
it's more svn-friendly as the revisions are per repository.
I have several and I know of others but few are as anal and bogged down
in politics as the Avalon process so most use slight modifications of
the dist/release plugin. Mauro has worked a bit on the release plugin so
maybe able to shed a bit of a better udnerstanding on it?
Anyhow I will check in a basic maven.xml to perform basics of release
process. I will skip generating mails and mailing them out as I think
that is something a user should do.
Looks good to me :-)
I'll try it out during the weekend on linux.
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Apache Excalibur Project -- URL: http://excalibur.apache.org/
