Affects Version/s: 2.3.1
Fix Version/s: more-investigation
Not sure if this is a bug or improvement...
- moduleA produces moduleA-1.2.3-test.jar with the jar:test-jar goal
- moduleB consumes moduleA-1.2.3-test.jar as a <dependency>...<scope>test</scope><dependency>
- When -Dmaven.test.skip=true the moduleA-1.2.3-test.jar is never built.
- Then when moduleB tries to build, it's moduleA-1.2.3-test.jar dependency is unresolved. FAIL! Even with -Dmaven.test.skip=true this will fail.
You might argue that this is a bug with dependency resolution with -Dmaven.test.skip=true - should a missing dependency @ test scope really fail the build??? It probably should - which is why the bug is submitted here
I've no idea what could be done to fix this either?
p.s. for anyone with this bug the only workaround I can suggest is running another module...
and have <dependency>...<artifactId>moduleA-test<artifactId>...<scope>test</scope></dependency>
|Workflow||jira [ 12959574 ]||Default workflow, editable Closed status [ 12996497 ]|
|Project Import||Mon Apr 06 00:05:23 UTC 2015 [ 1428278723217 ]|
|Workflow||jira [ 12722020 ]||Default workflow, editable Closed status [ 12759452 ]|
|Project Import||Sun Apr 05 10:31:03 UTC 2015 [ 1428229863560 ]|
|Fix Version/s||more-investigation [ 20439 ]|
|Attachment||MJAR-138-maven-jar-plugin.patch [ 59786 ]|