[
https://issues.apache.org/jira/browse/IVY-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maarten Coene resolved IVY-474.
-------------------------------
Resolution: Fixed
The strict conflictmanager now support basic support for dynamic revisions. All
dynamic revisions are resolved before they are passed to this conflict manager.
This means that revision 1.1 and 1.+ will only be compatible if 1.+ is resolved
to 1.1, which depends on the revisions available in the resolver.
If you need a more intelligent conflictmanager, you'll have to use the
compatible conflictmanager as mentioned by Xavier.
> Strict conflictmanager 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: 1.4.2, 2.0.0-alpha-2
> Environment: Ivy 1.5.0-incubating-dev-20070308022022 - 20070308022022
> Reporter: Robert Macaulay
> Assignee: Maarten Coene
> 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.
