dependency resolution fails when modules have inter-dependencies
----------------------------------------------------------------
Key: MNG-3816
URL: http://jira.codehaus.org/browse/MNG-3816
Project: Maven 2
Issue Type: Bug
Components: Artifacts and Repositories
Affects Versions: 2.0.9
Environment: Mac, Maven 2.0.9, Java 1.5
Reporter: Joshua Pollak
Attachments: demoPom.tgz
There seems to be problems with dependency resolution at various phases in the
maven lifecycle. For example, if I run the following command on the attached
project, I get a failure instead of the expected dependency tree:
[EMAIL PROTECTED]:~/src/software/projects/demoPom/trunk$ mvn dependency:tree
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Demo Project
[INFO] moduleA - Framework Code
[INFO] moduleB - Generated Sources
[INFO] moduleC - Main Application
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Demo Project
[INFO] task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:tree]
[INFO] com.kiva.demoPom:demoPom:pom:0.0.2-SNAPSHOT
[INFO] \- junit:junit:jar:3.8.1:test
[INFO] ------------------------------------------------------------------------
[INFO] Building moduleA - Framework Code
[INFO] task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:tree]
[INFO] com.kiva.demoPom:moduleA:jar:0.0.2-SNAPSHOT
[INFO] \- junit:junit:jar:3.8.1:test
[INFO] ------------------------------------------------------------------------
[INFO] Building moduleB - Generated Sources
[INFO] task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) com.kiva.demoPom:moduleA:jar:0.0.2-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.kiva.demoPom -DartifactId=moduleA
-Dversion=0.0.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.kiva.demoPom -DartifactId=moduleA
-Dversion=0.0.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]
Path to dependency:
1) com.kiva.demoPom:moduleB:jar:0.0.2-SNAPSHOT
2) com.kiva.demoPom:moduleA:jar:0.0.2-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
com.kiva.demoPom:moduleB:jar:0.0.2-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Mon Nov 03 17:00:13 EST 2008
[INFO] Final Memory: 9M/18M
[INFO] ------------------------------------------------------------------------
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
