You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2009/06/02 17:18:42 UTC

[jira] Commented: (MRELEASE-450) release:perform shoult 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=179007#action_179007 ] 

Olivier Lamy commented on MRELEASE-450:
---------------------------------------

configure your pom with 
{code:xml}
<arguments>-DskipTests</arguments>
{code}

> 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
>         Environment: linux
>            Reporter: Christian Hammers
>            Priority: Minor
>
> 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