Emmanuel Bourg
added a comment - 17/Oct/11 12:02 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

Sebb
added a comment - 17/Apr/13 17:54 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.