You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2010/01/04 00:26:55 UTC
[jira] Commented: (MRELEASE-450) release:perform should not call
test:test as release:prepare already did
[ http://jira.codehaus.org/browse/MRELEASE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204974#action_204974 ]
Paul Benedict commented on MRELEASE-450:
----------------------------------------
Performing the release is supposed to do a "clean room" build. Skipping the tests might be useful (speedier for sure), but it also is a way to release artifacts with failing tests. I say mark this as Won't Fix.
> release:perform should 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