maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SUREFIRE-826) maven-surefire-plugin does not add its own plugin dependencies to the classpath
Date Thu, 11 Jun 2015 08:16:01 GMT

    [ https://issues.apache.org/jira/browse/SUREFIRE-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581656#comment-14581656
] 

Tibor Digana commented on SUREFIRE-826:
---------------------------------------

Good point. 
I am fixing significant bugs, but writing good documentation always pays.
Please open pull-request in GitHub and mention few words about this issue in src/main/site/**/*.vm
in module maven-surefire-plugin.
Then I will assign this in 2.19.
Thx

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

Mime
View raw message