On 28 Sep 2012, at 4:13 PM, Jesse Long <j...@unknown.za.net> wrote: > My library does clearly document the versions of slf4j it depends on - as a > version range in the pom.xml file. How else? > > Never mind slf4j for the time being, this affects all libraries. > > Please see http://semver.org/ > > The whole purpose of having a major version number is to clearly indicate > when incompatibility is introduced. It does get introduced, often.
In turn, this is why maven goes on about repeatability - so that when you need to rebuild your code in an emergency to apply that critical bug fix to live, your code builds first time, every time. If you're someone like Redhat, and can hire a bunch of people to release packages with dependencies that follow the rule that ABI compatibility is maintained at all times, then you're fine. But if you're depending on various libraries released by various independent people and organisations with no guarantees of anything, then pinning the version numbers is the only sane thing to do. Regards, Graham --
smime.p7s
Description: S/MIME cryptographic signature
