Details
-
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
-
Labels:None
-
Number of attachments :
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'
-
-
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)
-
-
MNG-2871
Subartifact (ejb-client, test-jar etc.) are not reselved as active project artifacts in build phases prior to package
-
-
MNG-3023
Reactor projects should be included in dependency resolution
-
-
MNG-4248
CLONE -Maven can't compile against sibling test-jar dependency in multiproject (Test Attached)
-
-
MNG-249
compile and package should be reactor-aware
-
- relates to
-
MNG-4269
[regression] Invocation of just installed plugin on its plugin project can fail with ComponentLookupException for mojo class
-
-
MNG-4032
Test jar dependency not available for for main classes in multi module builds
-
-
MRELEASE-326
Doens't resolve multiproject dependencies properly
-
-
MNG-4071
Support additional read-only local repositories
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | Reviewed [ 13555 ] |
| Affects Version/s | 3.0 [ 13142 ] | |
| Fix Version/s | Reviewed Pending Version Assignment [ 13555 ] | |
| Fix Version/s | 2.0.x [ 13141 ] |
| Attachment | mng-3043.zip [ 40492 ] |
| Attachment | mng-3043.zip [ 40493 ] |
| Attachment | mng-3043.zip [ 40492 ] |
| Link |
This issue relates to |
| Assignee | Benjamin Bentmann [ bentmann ] | |
| Fix Version/s | 2.2.x [ 13141 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Fix Version/s | 3.0-alpha-3 [ 14719 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Reopened [ 4 ] | Closed [ 6 ] |