[
http://jira.codehaus.org/browse/MNG-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MNG-2873:
---------------------------
Affects Version/s: (was: 2.0.5)
2.0.10
can you make a sample project or IT?
> Unable to find transitive dependencies when they have been relocated.
> ---------------------------------------------------------------------
>
> Key: MNG-2873
> URL: http://jira.codehaus.org/browse/MNG-2873
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Reporter: Micah Whitacre
> Fix For: 2.0.10
>
>
> I have two projects A and B. Project A is dependent on B. Project B has
> compile time on project C which is deployed to a repository, repository1.
> The newest version, 2.0, of project C has since been relocated from
> oldGroupId to newGroupId. The relocation POMs are working correctly and
> Project B is able to be built successfully. Project A is not dependent on
> anything from repository1 it does not list that repository in its own
> <repositories/> section. When building project A, it tries to resolve the
> dependencies of B which includes C. However I am currently getting errors
> when it tries to resolve the C. Below is an example of this error occurring.
> As you can see the list of remote repositories does not display repository1
> as one of the repositories that was checked despite the fact that Project B
> listed it in its POM.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> No versions are present in the repository for the artifact with a range [1,)
> oldGroupId:projectC:jar:null
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> repo2 (http://repo.some-repo.com/repo)
> If I change project B to not use a range but to instead depend on a
> non-relocated version of project C everything works fine and I do not get
> this issue at all. The other and more correct solution to this issue is to
> update project B to use the new groupIds however it forces me to release
> project B immediately since all older released versions of B are broken by
> using the old groupIds an this issue.
--
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
