ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zsolt Szloboda (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IVY-223) A conflict manager that is able to allow implementation changes but not api changes (1.2.x - OK), (1.x.x - Not OK)
Date Sun, 30 Oct 2011 17:08:32 GMT

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

Zsolt Szloboda commented on IVY-223:
------------------------------------

I think there is still a problem with this conflict manager:
when there are more than one compatible dependencies
the *latest revision* should be choosen

eg if we have revisions 1.2.1 and 1.2.2
and we have a regexp that matches only the first two parts of the version numbers (1.2)
(so, in this case, 1.2.1 and 1.2.2 are considered compatible)
1.2.2 should always be choosen (1.2.1 should be evicted)

at the moment, 1.2 is compared with 1.2
(but, I think, 1.2.1 should be compared with 1.2.2)

                
> A conflict manager that is able to allow implementation changes but not api changes (1.2.x
- OK), (1.x.x - Not OK)
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-223
>                 URL: https://issues.apache.org/jira/browse/IVY-223
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Anders Janmyr
>            Assignee: Xavier Hanin
>            Priority: Minor
>             Fix For: 1.4-RC1
>
>         Attachments: RegexpConflictManager.java, RegexpConflictManagerTest.java, ivy-conflict.xml,
ivy-no-regexp-conflict.xml, ivyconf-regexp-test.xml
>
>
> We have a situation where our api changes are characterized by the first two version
numbers and the third number characterizes implementation changes.
> 1.2.3 --> 1.2 5 --> 1.2.10 are implementation changes
> whereas
> 1.2.3 --> 1.3.0 --> 2.0.0 are API changes.
> We don't want the implementation changes to cause conflicts but the api changes must
be signalled as conflicts.
> I have implemented a simple RegexpConflictManager for this and I'll try to attach it
to this issue.
> Anders

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message