[jira] Commented: (IVY-160) Duplicate dependency entries within one Ivy-File not resolved correctly

["Xavier Hanin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IVY-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12506726 ] 

Xavier Hanin commented on IVY-160:
----------------------------------

I'm not sure if and how we should fix this issue. Ivy has never been meant to support this kind of construct: you should declare a dependency on one module only in one dependency element. So a fix could be to raise an error in this case, but I know that some people declare several dependencies on the same module with different versions. I even think there is an issue for it, because it doesn't work properly. But I don't see how and if we can really support this kind of things.

Thoughts?

> 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
>            Assignee: Xavier Hanin
>            Priority: Minor
>             Fix For: 2.0
>
>
> 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.