You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Aslak Knutsen (JIRA)" <ji...@codehaus.org> on 2013/01/16 20:32:13 UTC

[jira] (SUREFIRE-762) Add support for test compile and test runtime separation

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

Aslak Knutsen updated SUREFIRE-762:
-----------------------------------

    Attachment: SUREFIRE-762

Git Commit: https://github.com/aslakknutsen/maven-surefire/commit/e914da14c12f96b042bad92f703d57e64f59276c

Adds the 'additionalProfiles' configuration option. The additional profile ids are used to activated the profile to re calculate the TestClasspath and open up for runtime only dependencies.

Used in cases where you e.g. only want API on classpath but test against a specific impl. Individual Surefire Executions can be configured to run against different API impls. 
                
> Add support for test compile and test runtime separation
> --------------------------------------------------------
>
>                 Key: SUREFIRE-762
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-762
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Maven Surefire Plugin
>    Affects Versions: 2.9
>            Reporter: Aslak Knutsen
>         Attachments: SUREFIRE-762
>
>
> In some cases it is interesting to bind surefire to multiple execution targets but have it operate on different classpaths. 
> e.g:
> - Have the same test suite run against multiple JPA providers; EclipseLink and Hibernate
> - Arquillian test suite run against Tomcat and Jetty
> In these cases you would have the TestCompile scope defined in your normal dependency chain scoped as "test", while you can tell surefire to activate another profile during test.
> TestCompile = JPA API
> TestRuntime = Hibernate | EclipseLink
> Example:
> https://gist.github.com/1155271

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira