On Sat, 28 May 2011, sebb wrote:
So IMO if we want to change the groupid or make small incompatible
changes it would be OK.
Changing the groupId without changing the package name can result in
two copies of the library on the classpath, which is much harder to
debug than a binary API change. It's not essential to change the
groupId, so why run the risk?
BTW, the current code is binary compatible with 1.3.1.
OK, on the basis of all this, I think we should stick with the current
groupId for 1.4
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
