this was incorrectly closed as fixed instead of incomplete
On 6/14/07, Jason van Zyl (JIRA) <[EMAIL PROTECTED]> wrote:
[
http://jira.codehaus.org/browse/MNG-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-3052.
------------------------------
Resolution: Fixed
Incomplete provide a sample build to illustrate the problem.
> 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
>
> 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
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
