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...@apache.org> on 2015/06/21 23:28:00 UTC

[jira] [Updated] (SUREFIRE-826) maven-surefire-plugin does not add its own plugin dependencies to the classpath

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

Tibor Digana updated SUREFIRE-826:
----------------------------------
    Fix Version/s: 2.19

> maven-surefire-plugin does not add its own plugin dependencies to the classpath
> -------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-826
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-826
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: classloading, Maven Surefire Plugin
>    Affects Versions: 2.11
>         Environment: Maven 3.0.3
> Java 6
>            Reporter: René Zanner
>            Assignee: Tibor Digana
>             Fix For: 2.19
>
>
> Currently some JAR containing a RunListener for JUnit must be located in the project's classpath (and pollutes the classpath with most likely unwanted transitive dependencies).
> An alternative is to use the 'additionalClasspathElements' configuration element in the maven-surefire-plugin's configuration. Unfortunately this cannot be used to specify another maven artifact directly - only JARs or class folders in the file system.
> It would be consistent to enable the usage of plugin dependencies ({{<dependencies>}} element in the {{<plugin>}} section of the POM) to load such classes:
> {code:xml}
> <plugin>
>     <artifactId>maven-surefire-plugin</artifactId>
>     <configuration>
>         <properties>
>             <property>
>                 <name>listener</name>
>                 <value>some.RunListener</value>
>             </property>
>         </properties>
>     </configuration>
>     <!-- 
>         reference the JAR containing the class some.RunListener as plugin dependency 
>         (this is possible from the Maven point of view, but currently does not work) 
>     -->
>     <dependencies>
>         <dependency>
>             <groupId>some.group.id</groupId>
>             <artifactId>some-artifact-id</artifactId>
>             <version>${some.version}</version>
>         </dependency>
>     </dependencies>
> </plugin>
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)