[
http://jira.codehaus.org/browse/MRELEASE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190272#action_190272
]
Chris Kneeland commented on MRELEASE-450:
-----------------------------------------
I have to agree with Mark. It's very rare, but I have had prepare "pass" tests,
to only fail when doing a perform and they were valid fails with the tests.
Although it is a pain that the artifact was able to tag, at least in perform
the tests caught the error and the artifact was not deployed to the mvn repo.
I'm also one who does builds with a few machines and I feel better when the
tests are run on both prepare and peform, especially on different environments
and time has elapsed.
> release:perform shoult not call test:test as release:prepare already did
> ------------------------------------------------------------------------
>
> Key: MRELEASE-450
> URL: http://jira.codehaus.org/browse/MRELEASE-450
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.0-beta-9
> Environment: linux
> Reporter: Christian Hammers
> Assignee: Olivier Lamy
> Priority: Minor
> Fix For: 2.0-beta-10
>
>
> Hello
> When doing a "mvn release:prepare" and then "mvn release:perform" the
> complete test suite is run twice. As it takes a couple of minutes it feels
> annoying. Also I don't really see the necessarity of running the test:test
> goal in release:perform as release:prepare already does so and afterwards tag
> the source code so that the perform cannot be made on a non-tested code, or?
> bye,
> -christian-
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
