maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Rosenvold (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (SUREFIRE-595) Add surefire:force-test mojo to postpone tests
Date Fri, 24 Dec 2010 21:11:57 GMT

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

Kristian Rosenvold updated SUREFIRE-595:
----------------------------------------

    Component/s: Maven Surefire Plugin

> 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
>          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 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

        

Mime
View raw message