[jira] Updated: (SUREFIRE-595) Add surefire:force-test mojo to postpone tests

["Dan Fabulich (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/SUREFIRE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Fabulich updated SUREFIRE-595:
----------------------------------

    Comment: was deleted

(was: Note that this is also useful in single-threaded builds; in many cases running the build like this will help the build to discover compile failures faster than the standard lifecycle.  (Of course, in single-threaded mode it discovers test failures slower, so there's a trade-off there.))

> Add surefire:force-test mojo to postpone tests
> ----------------------------------------------
>
>                 Key: SUREFIRE-595
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-595
>             Project: Maven Surefire
>          Issue Type: New Feature
>            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 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