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

Johannes Stamminger commented on IVY-537:
-----------------------------------------

OK, I see your point. And the more I think about it, I believe the current 
behaviour in 1.4.1 to be the correct one - to fail (and therefore to be false 
in 2.0.x currently).

In my special situation (it is a license file that was renamed) then an 
explicite exclude definition in my dependency to moduleB would be appropriate. 
Unfortunately the exclude seems to work only for a whole module. More detailed 
exclusions (by type, name, ...) are not regarded and the resolve fails again 
:-(. But I will go into that more deep tomorrow.


btw: just extract my attached example ant type 'ant' - then you get 
dependencies reports/graphs in a new subdir build/dependencies. The most 
interesting ones are those concerning the deployment configuration.

> Eviction fails for libs not providing their ivy configuration and providing 
> artifacts named different between lib versions
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-537
>                 URL: https://issues.apache.org/jira/browse/IVY-537
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: Johannes Stamminger
>         Attachments: ivy-lib-eviction.zip
>
>
> With moduleA referencing libX-1.0 with:
>         <dependency name="libX" rev="1.0" org="COTS" conf="compile, 
> development, deployment">
>             <artifact name="libX" conf="compile"/>
>             <artifact name="LICENSE" type="license" ext="txt" 
> conf="deployment"/>
>             <artifact name="libX" type="source" ext="src.jar" 
> conf="development"/>
>         </dependency>
> and another module referencing same libX but in version 2.0 by way of:
>         <dependency name="libX" rev="2.0" org="COTS" conf="compile, 
> development, deployment">
>             <artifact name="libX" conf="compile"/>
>             <artifact name="libX" type="license" ext="jar.license" 
> conf="deployment"/>
>             <artifact name="libX" type="source" ext="src.jar" 
> conf="development"/>
>         </dependency>
> the eviction of libX-1.0 fails (note the different namings for the license 
> artifact).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to