[
https://issues.apache.org/jira/browse/IVY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544496
]
Gilles Scokart commented on IVY-586:
------------------------------------
I have added the code to also handle the relocation of the artefactId and
version number. Unfortunately, it is not enought because a module is not
authorized to depend on itself.
And in this case, we end up with [ xml-apis | xml-apis | 2.0.2 ] depending on [
xml-apis | xml-apis | 1.0.b2 ].
So the simple aproach I took was too simplist ;-)
Making the change in PomModuleDescriptorParser is thus probably not enought.
Also, I'm not sure how conflict resulution should be performed in case of
relocation...
I will left the code as it is because it handle simple relocation (orgnaisation
or artefact, without conflict managment involved)
But I keep the issue open until we find a better solution.
> ivy doesn't handle relocation in pom.xml
> ----------------------------------------
>
> Key: IVY-586
> URL: https://issues.apache.org/jira/browse/IVY-586
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha-1
> Reporter: Gilles Scokart
> Assignee: Gilles Scokart
> Priority: Critical
> Fix For: 2.0.0-beta-1
>
>
> See for example :
> http://repo1.maven.org/maven2/dbunit/dbunit/2.2/dbunit-2.2.pom
> ivy, ignore the relocation content, and try to donwload the jar from
> http://repo1.maven.org/maven2/dbunit/dbunit/2.2/ (which doesn't exist)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
