On 17 February 2015 at 22:56, Peter Ansell <ansell.pe...@gmail.com> wrote: > On 17 February 2015 at 21:48, sebb <seb...@gmail.com> wrote: >> On 17 February 2015 at 06:13, Benedikt Ritter <brit...@apache.org> wrote: > > <snip, sounds good> > >>> and the maven coordinates when we break binary compatibility (= bump up the >>> major version number). We do this to avoid jar hell. This way two versions >>> of the same commons library can be in the same classpath. >> >> I hope most other projects with Maven jars do the same, particularly >> ones which are libraries. >> I know HttpComponents does. > > I haven't noticed many projects changing their Maven coordinates when > bumping the major version number, but it is useful for those reasons, > as long as the package names inside also change.
I would hope all projects increase the major version when breaking compat. But some may well use a major version bump to denote large increases in functionality etc. This is not strictly SemVer, but if the API is well designed from the outset there may be no need to break compatibility for many years. Minor version increments then may not reflect the functionality improvement. Version numbers are not just technical qualifiers, they may also play a role in how the product is perceived. If binary compat is maintained, the package/Maven ids should remain the same. > Cheers, > > Peter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
