You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tibor Digana (JIRA)" <ji...@codehaus.org> on 2015/01/04 14:41:10 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 ]

Tibor Digana reassigned SUREFIRE-762:
-------------------------------------

    Assignee: Tibor Digana

> 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
>            Assignee: Tibor Digana
>         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 was sent by Atlassian JIRA
(v6.1.6#6162)