maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Updated: (MNG-3043) Allow 'mvn test' to work with test-jar dependencies in a reactor
Date Sat, 07 Mar 2009 14:28:13 GMT


Benjamin Bentmann updated MNG-3043:


Sample project.

> Allow 'mvn test' to work with test-jar dependencies in a reactor
> ----------------------------------------------------------------
>                 Key: MNG-3043
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Dependencies, Reactor and workspace
>    Affects Versions: 2.0.6, 2.0.7
>            Reporter: Kenney Westerhof
>             Fix For: 2.0.x
>         Attachments:
> Basically the issue is demonstrated by MNG-2045, but instead of running 'mvn install',
you run 'mvn test'.
> Test classes of dependencies should be resolved from the reactor, just as main classes,
if there's no archive available.
> I'm not sure how to go about this. Specifying a dependency on something with <type>test-jar</type>,
> and having that dependency declare the maven-jar-plugin with the 'test-jar' goal is insufficient.
> Perhaps we can just add a standard classifier that maven is aware of, in this case 'tests'.
The jar packaging
> would export this as a known classifier, and tells maven how it contributes to what classpath.
> Since test sources are a first class citizen, just as main sources are (they have the
same phases, same
> elements in the pom (but differently named)).
> It seems logical to me that somehow the test classes should be made available to dependencies,
> if they declare a dependency with classifier 'tests'.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message