Uploaded image for project: 'Ivy'
  1. Ivy
  2. 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)

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 1.4-RC1
    • Core
    • None

    Description

      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

      Attachments

        Activity

          People

            xavier Xavier Hanin
            gigant Anders Janmyr
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: