[
https://issues.apache.org/jira/browse/IVY-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521644
]
Nascif Abousalh-Neto commented on IVY-474:
------------------------------------------
Same problem, using 1.4.1, the strict manager and the "latest.release" wildcard:
[ivy:resolve] ERROR: [ TPJ | Log4J | latest.release ] (needed by [ SAS |
sas.svcs.data | [EMAIL PROTECTED] ]) conflicts with [ TPJ | Log4J | 1.2.13 ]
(needed by [ TPJ | commons_logging | 1.1.0 ])
This greatly reduces the usability of wildcards and ranges! If all users of a
dependency have to stay in synch with the version number at all times, it won't
be able to scale Ivy to large organizations. It would take too much effort to
synchronize all the teams to stay on the same exact version when a new version
is introduced.
> Conflict manager seems to not support dynamic revisions
> -------------------------------------------------------
>
> Key: IVY-474
> URL: https://issues.apache.org/jira/browse/IVY-474
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: unspecified
> Environment: Ivy 1.5.0-incubating-dev-20070308022022 - 20070308022022
> Reporter: Robert Macaulay
> Fix For: 2.0
>
>
> If I use defaultConflictManager="strict"
> I get this
> [ extern | commons-logging | 1.1 ] (needed by [[ extern | spring-framework |
> 2.0.2 ], [ ubs | laredo | [EMAIL PROTECTED] ]])
> conflicts with [ extern | commons-logging | [1.0.4,) ] (needed by [[extern |
> hibernate | 3.2.1 ]])
> It looks like the strict ConflictManager does not support dynamic ranges. 1.1
> != [1.0.4,) One package is requesting 1.1, the other is asking for 1.0.4 or
> greater.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
