You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2008/06/25 13:11:45 UTC
[jira] Updated: (IVY-160) Duplicate dependency entries within one
Ivy-File not resolved correctly
[ https://issues.apache.org/jira/browse/IVY-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin updated IVY-160:
-----------------------------
Fix Version/s: (was: 2.0)
> Duplicate dependency entries within one Ivy-File not resolved correctly
> -----------------------------------------------------------------------
>
> Key: IVY-160
> URL: https://issues.apache.org/jira/browse/IVY-160
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 1.2, 1.3-RC1
> Environment: OS Windows
> Reporter: Nils Tegtmeier
> Priority: Minor
>
> If an ivy.xml contains more than one <dependency>-entry for the same organisation and module, only one of them is resolved correctly. This issue showed itself in two different flavors:
> a)
> Suppose you have two subsequent entries for identical configurations like this:
> <dependency org="foo" name="bar" rev="1.5+" >
> <conf name="runtime">
> <mapped name="*" />
> </conf>
> <artifact name="gumbo" type="zip" />
> </dependency>
> <dependency org="foo" name="bar" rev="1.5+">
> <conf name="runtime">
> <mapped name="*" />
> </conf>
> <artifact name="okra" type="jar"/>
> </dependency>
> Then the first is resolved and retrieved while the second is not.
> b)
> Suppose you have two subsequent entries for different configurations like this:
> <dependency org="foo" name="bar" rev="1.2.1">
> <conf name="compile">
> <mapped name="*"/>
> </conf>
> <artifact name="gumbo" type="jar"/>
> </dependency>
> <dependency org="foo" name="bar" rev="1.2.1">
> <conf name="runtime">
> <mapped name="*"/>
> </conf>
> <artifact name="okra" type="jar"/>
> </dependency>
> Then both are resolved to the configuration of the first entry if you call <ivy:resolve file="/ivy.xml" conf="*"/>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.