[
https://jira.codehaus.org/browse/MRELEASE-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg closed MRELEASE-700.
----------------------------------
Resolution: Won't Fix
Assignee: Mark Struberg
Hi Oleg!
I had the same discussion already a long time ago. The rational behind this is
that people tend to skip tests way too often. But you usually really should not
skip tests when doing a release.
So - there is a way (as you gladly found out) - but it requires to not go the
default route. And this is imo a good thing which is a welcome side effect of
the way the maven-release-manage works.
> 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
