[
https://jira.codehaus.org/browse/MRELEASE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275335#comment-275335
]
Mark Struberg commented on MRELEASE-700:
----------------------------------------
heh another long time goodie ;)
The reason why tests are both executed in prepare and perform are:
* in release:prepare to not create a tag if a test is broken
* in release:perform to make sure that the build still runs file on a clean
checkout (remember: mvn release:perform will checkout to ./target/checkout/ and
runs all the build there).
I had it a few times that my build did only work because I had something
locally which was not checked in. Classic candidates are modified
build.properties from an integrated antrun, etc
> release:prepare -Dmaven.test.skip=true should work
> --------------------------------------------------
>
> Key: MRELEASE-700
> URL: https://jira.codehaus.org/browse/MRELEASE-700
> Project: Maven 2.x Release Plugin
> Issue Type: Wish
> Components: prepare
> Affects Versions: 2.1
> Environment: maven 3.0.3
> Reporter: Oleg Mayevskiy
> Assignee: Mark Struberg
> Priority: Minor
>
> currently if i want to skip tests during a prepare or perform phase, i must
> do the following:
> mvn release:prepare arguments='-Dmaven.test.skip=true'...
> It would be more intuitive, if mvn -Dmaven.test.skip=true would work.
> This is the default way, how tests are disabled in maven.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
