LatestRevisionStrategy has split personality
--------------------------------------------
Key: IVY-383
URL: https://issues.apache.org/jira/browse/IVY-383
Project: Ivy
Issue Type: Bug
Components: Core
Affects Versions: 1.4.1
Environment: all
Reporter: John Williams
Priority: Critical
LatestRevisionStrategy seems to compare both revision numbers and revision
number patterns, but the implementation of patterns broken. For instance,
patterns like "1.0+" are treated specially, but patterns like "[1.0,)" are
treated like literal revision numbers! I have a case in which this causes
conflict resolution to produce incorrect results. I'll hopefully be posting a
patch soon to fix the particular resolution problem I've found, but I'm
suspicious that there are other cases in which patterns are erroneously passed
to LatestRevisionStrategy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
