Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-alpha1, 4.0
    • Component/s: None
    • Labels:
      None

      Activity

      Hide
      Emmanuel Bourg added a comment -

      I believe this will be done only when the package name has to be changed due to backward incompatibilities.

      Show
      Emmanuel Bourg added a comment - I believe this will be done only when the package name has to be changed due to backward incompatibilities.
      Hide
      Olivier Lamy (*$^¨%`£) added a comment -

      yup exactly.
      Do we apply same logic as with lang ? org.apache.commons.collections4 ?

      Show
      Olivier Lamy (*$^¨%`£) added a comment - yup exactly. Do we apply same logic as with lang ? org.apache.commons.collections4 ?
      Hide
      Emmanuel Bourg added a comment -

      I'm not sure there is a consensus to break the compatibility yet. The latest discussion in august suggested that the next release would introduce generics while preserving the compatibility:

      http://markmail.org/thread/ditp2qnqjehxkx3w

      Show
      Emmanuel Bourg added a comment - I'm not sure there is a consensus to break the compatibility yet. The latest discussion in august suggested that the next release would introduce generics while preserving the compatibility: http://markmail.org/thread/ditp2qnqjehxkx3w
      Hide
      Sebb added a comment -

      The groupId and/or artifactId must be changed when the package name is changed.

      Given that the groupId is currently non-standard, it makes sense to change it to o.a.c

      That means the artifactId could be left as "commons-collections".
      However, I think it would be less confusing to use "commons-collections4".

      Then next time a binary break is needed, package and artifactId would remain in step.

      Show
      Sebb added a comment - The groupId and/or artifactId must be changed when the package name is changed. Given that the groupId is currently non-standard, it makes sense to change it to o.a.c That means the artifactId could be left as "commons-collections". However, I think it would be less confusing to use "commons-collections4". Then next time a binary break is needed, package and artifactId would remain in step.
      Hide
      Matt Benson added a comment -

      I thought we had decided as a PMC to use commons-collections4 etc. going forward as Seb suggests.

      Show
      Matt Benson added a comment - I thought we had decided as a PMC to use commons-collections4 etc. going forward as Seb suggests.
      Hide
      Thomas Neidhart added a comment -

      Changed to maven coordinates org.apache.commons.commons-collections4 in r1469010.

      Show
      Thomas Neidhart added a comment - Changed to maven coordinates org.apache.commons.commons-collections4 in r1469010.

        People

        • Assignee:
          Unassigned
          Reporter:
          Olivier Lamy (*$^¨%`£)
        • Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development