FYI
I found some clues on how to deal with branches based on the code of the
PerformReleaseMojo and the PrepareReleaseMojo.
1) release:prepare works on a checked out project. This allows for
tagging to be made on the correct branch.
2) release:perform works by checking out the project based on a tag. I'm
assuming that tags in CVS has to be unique across branches.
I had a look at at branches made for maven/components on svn.apache.org,
but I got somewhat confused (I'm not so familiar with SVN yet).
Is the branch and tag information kept in the scm url of the parent pom
for maven/component?
Anyhow... It works, but now I can not understand what the <tag> element
in the <scm> section is good for? :-)
Ørjan
Orjan Austvold wrote:
We're using Maven 2 with CVS on several multi-module projects and we
have successfully performed releases in the last 3 months.
Yesterday we ran into problems with releases on a CVS branch.
I added a <tag> on the <scm> element for the parent pom on the branched
project. When I did a release the pom checked in by the release plugin
actually removed the <tag> element.
Am I using the wrong element for describing the branch name or should I
file a bug on the release plugin?
Thanks,
Ørjan
---------------------------------------------------------------------
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]
