[
https://jira.codehaus.org/browse/MNG-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=330786#comment-330786
]
Stephen Connolly commented on MNG-5503:
---------------------------------------
This appears to me to be a blocking regression.
Your test case has some minor issues that make it harder to identify the root
cause (would have been better if all the versions were -SNAPSHOT versions...
but none-the-less it does identity a major regression IMHO.
Here is the build output:
{code}
$ mvn clean verify
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] module-a
[INFO] module-b
[INFO] parent
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building module-a 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ module-a ---
[INFO] Deleting /Users/stephenc/tmp/mng5503/rep/module-a/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ module-a
---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/Users/stephenc/tmp/mng5503/rep/module-a/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ module-a ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
module-a ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/Users/stephenc/tmp/mng5503/rep/module-a/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @
module-a ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ module-a ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ module-a ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar:
/Users/stephenc/tmp/mng5503/rep/module-a/target/module-a-1.0.0-SNAPSHOT.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.2-beta-5:single (assemble) @ module-a ---
[INFO] Reading assembly descriptor: zip.xml
[INFO] Building zip:
/Users/stephenc/tmp/mng5503/rep/module-a/target/module-a-1.0.0-SNAPSHOT.zip
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building module-b 1.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] module-a .......................................... SUCCESS [1.852s]
[INFO] module-b .......................................... FAILURE [0.018s]
[INFO] parent ............................................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.034s
[INFO] Finished at: Fri Aug 16 15:08:26 IST 2013
[INFO] Final Memory: 11M/208M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project module-b: Could not resolve
dependencies for project
org.fedoraproject.rhbz991454:module-b:jar:1.0.0-SNAPSHOT: Could not find
artifact org.fedoraproject.rhbz991454:module-a:zip:1.0.0-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :module-b
{code}
I have removed the debug output, but essentially what seems to be happening is
that it is looking for the metadata for the artifact outside of the reactor in
order to determine whether or not the artifact with that specific classifier is
present. I suspect, but I have not proved, that if the metadata was present
(e.g. from having run as far as the install phase) then the artifact would be
resolved from the reactor... but I'd like confirmation of that before
downgrading this issue from blocker.
Jason, assigning to you as you're running the 3.1.1 release
> Maven 3.1.0 fails to resolve artifacts produced by reactor build
> ----------------------------------------------------------------
>
> Key: MNG-5503
> URL: https://jira.codehaus.org/browse/MNG-5503
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.1.0
> Reporter: Severin Gehwolf
> Assignee: Jason van Zyl
> Priority: Blocker
> Fix For: 3.1.1
>
> Attachments: reproducer-zip-type-deps.zip
>
>
> Maven 3.1.0 fails to resolve zip type dependencies produced via assemblies by
> modules higher up the reactor hierarchy. For example module A has a dep on
> module B of type zip. Module A produces a zip containing jars plus some other
> files which the build of module B should extract and copy to the output
> directory. However, dep solving of module B fails.
> It works with Maven 3.0.5 but fails to build with Maven 3.1.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
