[
https://jira.codehaus.org/browse/MRELEASE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292044#comment-292044
]
James Nord commented on MRELEASE-739:
-------------------------------------
I can't specify validate if the pom (or one of its parents) define the goals.
You would then need to modify the pom (which then changes what the actual
release (as the pom has changed).
(even validate can sometimes take a while in an enforced corporate world - or
validate could fail)
Shy sometimes?
I can think of a few reasons.
1) you want to separate building and reporting - but have both be able to run
easily
(mvn release:prepare & mvn release:checkout -D choukout = target/checkout1 &&
cd target/checkout1 && mvn deploy && cd .. && mvn release:checkout -D
checkout=target/checkout2 && mvn site clover:aggregate site-deploy && cd .. &&
release:clean
you don't want the reporting which is slow - to stop the release artifacts
being available.
You want to do this from a CI environemnt and want to utilse the CI environment
to intercept building to record artifacts
There are possibly more that this would enable but the above 2 are what I am
thinking of.
Hope that helps.
> Add a checkout goal
> -------------------
>
> Key: MRELEASE-739
> URL: https://jira.codehaus.org/browse/MRELEASE-739
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.2.2
> Reporter: James Nord
>
> It would sometimes be useful to be able to run release:prepare and then get a
> checkout of the source in target/checkout that comes from the tag that is
> just made.
> Whilst this is partially possible by using the maven-scm-plugin it does not
> understand the release.properties file so you need to parse that and then
> supply options to the command line.
> this request is to add a new goal "checkout" which will use the
> release.properties (or optionally configured parameters) to checkout the
> source.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
