[
http://jira.codehaus.org/browse/MNG-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Micah Whitacre updated MNG-3052:
--------------------------------
Attachment: mng_3052.zip
I hacked up Dirk's example (thanks for giving me a starting point) and created
an example that illustrates my point. Inside the zip file you will find three
projects, foo, bar, and wombat. Wombat depends on Bar which depends on Foo.
Using the projects in the zip file, run "mvn clean deploy" on foo and then bar.
After that is completed clear out your local repository and try and run "mvn
clean compile" on wombat. It will have an issue being able to resolve foo and
I get the following output:
Missing:
----------
1) org.mule:mule-foo:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.mule -DartifactId=mule-foo -Dversio
n=1.0-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=org.mule -DartifactId=mule-foo -Dversion=
1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id
]
Path to dependency:
1) org.mule:mule-wombat:jar:1.0-SNAPSHOT
2) org.mule:mule-bar:jar:1.0-SNAPSHOT
3) org.mule:mule-foo:jar:1.0-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
org.mule:mule-wombat:jar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
example2-repo (file://c:/test/repo2)
You'll notice that it never lists example1-repo as a repository it checked to
find foo.
> Transitive Dependency not found when repo is not listed
> -------------------------------------------------------
>
> Key: MNG-3052
> URL: http://jira.codehaus.org/browse/MNG-3052
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Micah Whitacre
> Priority: Critical
> Attachments: InheritLegacyRepo.zip, mng_3052.zip
>
>
> I have seen the situation where a build fails because a project has a
> transitive dependency that only exists in a repository not listed by my
> project. An example of this is I have Projects A, B, and C. Where A depends
> on B, and B on C. B has been released to remote repo 1, and C has been
> released to remote repo 2. Since A just directly depends on B it only lists
> remote repo 1 in its POM. However when I try to build project A the build
> fail because it can't resolve its transitive dependency C in any of the
> dependencies it is checking (repo 1 only).
> It is my understanding that for project A I shouldn't have to list the remote
> repos to resolve transitive dependencies. I should only have to list the
> repos to get to B and Maven then should use the POM of B to resolve C.
> Is that not correct?
--
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
