[
https://jira.codehaus.org/browse/SUREFIRE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356155#comment-356155
]
Tibor Digana commented on SUREFIRE-595:
---------------------------------------
@Dan, this is against the idea of Maven. I understand the lifecycle in the way
that the article should not be made public (installed or deployed) unless all
the tests passed.
If you want to install the article to your local repository, then you can still
use maven-invoker-plugin with IT tests and pre-install your article
http://maven.apache.org/plugins/maven-invoker-plugin/plugin-info.html
Dan, I would close this issue. This issue does not sound like a new feature.
IMHO you can use invoker instead.
Any objections to close this issue?
> Add surefire:force-test mojo to postpone tests
> ----------------------------------------------
>
> Key: SUREFIRE-595
> URL: https://jira.codehaus.org/browse/SUREFIRE-595
> Project: Maven Surefire
> Issue Type: New Feature
> Components: Maven Surefire Plugin
> Reporter: Dan Fabulich
>
> The standard lifecycle does all testing before installing artifacts in the
> local repository. When running our experimental concurrent Maven, we find
> that doing compiling/packaging/installing before testing can promote better
> concurrency.
> It would be helpful to have a surefire:force-test mojo, which simply extends
> the standard mojo but ignores the -DskipTests and -Dmaven.test.skip
> properties. That way, you could run the build like this:
> mvn install -DskipTests surefire:force-test
> The tests would be skipped during the install lifecycle, and then run
> separately at the end of the build.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
