[MNG-3043] Allow 'mvn test' to work with test-jar dependencies in a reactor

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.6, 2.0.7
• Fix Version/s: 3.0-alpha-3
• Component/s: Dependencies, Reactor and Workspace
• Assignee: Benjamin Bentmann
• Reporter: Kenney Westerhof
• Created: 08/Jun/07 14:12
• Updated: 21/Dec/22 10:57
• Resolved: 03/Aug/09 05:55

Description

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'.

Issue Links

• depends upon: MJAR-75 [PATCH] Wrong artifact type attached to the project by the test-jar goal
• is duplicated by: MNG-3076 Dependency on test-jar is not resolved with 'package' target, must use 'install'
• is duplicated by: MNG-4655 'mvn test' tries to locate tests jar of other module in repository
• is related to: MNG-2045 Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
• is related to: MNG-2871 Subartifact (ejb-client, test-jar etc.) are not reselved as active project artifacts in build phases prior to package
• is related to: MNG-3023 Reactor projects should be included in dependency resolution
• is related to: MNG-4248 CLONE -Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
• is related to: MNG-249 compile and package should be reactor-aware
• relates to: MNG-7629 Improve resolution of modules within a multi-module build
• relates to: MNG-4269 [regression] Invocation of just installed plugin on its plugin project can fail with ComponentLookupException for mojo class
• relates to: MNG-4032 Test jar dependency not available for for main classes in multi module builds
• relates to: MRELEASE-326 Doens't resolve multiproject dependencies properly
• relates to: MNG-4071 Support additional read-only local repositories