ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (IVY-586) ivy doesn't handle relocation in pom.xml
Date Mon, 03 Dec 2007 11:20:43 GMT

     [ https://issues.apache.org/jira/browse/IVY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gilles Scokart reassigned IVY-586:
----------------------------------

    Assignee:     (was: Gilles Scokart)

I have committed a change that allows to handle the case of xml-api (relocated to an other
version of itself).

In that that case, I pick-up the dependies of the relocation and I add them to the relocated
pom.  That means that we might still have problems to get the artefact.

In case of relocation to an other group/module, the relocation is just added as a dependency.

In both case, the complete solution should consider the relocated element as if it had never
existed.  But this requires changes in the resolution algorithm, and it also impose to check
every evicted element to be sure it has not been relocated to something that wouldn't be evicted.

So indeed, the complete implementaion should be reported to alter.


> 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
>            Priority: Critical
>             Fix For: 2.0
>
>
> 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.


Mime
View raw message