[
https://issues.apache.org/jira/browse/IVY-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
david herviou updated IVY-1178:
-------------------------------
Attachment: jira-ivy-1178.zip
Finally found the real-life use case that turns my head upside-down !
Attachment contains a simple project for identifying it. By default the
conflitManager is on latest-revision. If you run ant retrieve, the task will
failed because transitives dependencies are tried to be retrieved.
Switch the conflictManager to 'all' and the problem disappeared. The previous
workaround is still available.
> Transitive dependencies resolutions issue when eviction is triggered
> --------------------------------------------------------------------
>
> Key: IVY-1178
> URL: https://issues.apache.org/jira/browse/IVY-1178
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.1.0
> Environment: Linux / ant 1.7.0
> Reporter: david herviou
> Attachments: jira-ivy-1178.zip
>
>
> Originally described in ivy-user list :
> http://old.nabble.com/Transitive-resolving-issue---td27984462.html
> Here just a part of the discussion that explain the problem and the temporary
> work around :
> Consider the following use case :
> moduleA has one of its dependencies like this :
> <dependency org="log4j" name="log4j" rev="1.2.14" transitive="false"/>
> moduleB has one of its dependencies like this :
> <dependency org="log4j" name="log4j" rev="1.2.15" transitive="false"/>
> While moduleC use moduleA and moduleB I have something like this :
> <dependency org="moduleA.org" name="moduleA" rev="moduleA.rev"/>
> <dependency org="moduleB.org" name="moduleB" rev="moduleB.rev"/>
> This seems to be very banal BUT, when running the ivy:resolve task the
> log4j-1.2.15 evicts the log4j-1.2.14 which seems to be a good thing!
> but thereafter the resolve task does not consider the transitivity has false
> and try to resolve all the dependencies of log4j-1.2.15
> If I remove moduleA.org and use only moduleB.org then the resolve task
> behave correctly (I mean there is no resolution of transitives
> dependencies).
> The reverse case is also true.
> A work-around is available by resolving conflict explicitly with something
> like :
> <conflict org="moduleA.org" module="moduleA" rev="moduleA.rev"/>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
