Jader Francia 4 Years Ago Hey David! This post completely blow my mind! ;) You, obviously, are right; thank you for pointing us the "problem" out! ;) Please sign in to reply. Reply as... Cancel
Laurent REMY 4 Years Ago Hi David, thanks for the post! Very useful indeed and it seems developers are the same all around the world :) One question maybe: couldn't we use the bnd tool to automatically put the version? The real question behind this is: is the tool trustable enough so that we can skip the versioning decision and leave it to the tool? Laurent Please sign in to reply. Reply as... Cancel David H Nebinger Laurent REMY 4 Years Ago The tool is solid, but it is not a code analysis tool. It really doesn't know what class changes have gone on in a package from build to build and won't know what the versions should be. It also wouldn't be able to distinguish between a minor version bump and a major version bump... I admit that I am terrible at package versioning. I religiously maintain javadocs on the classes and methods that I write, but I will totally forget to go back and update the package versions... I wish there was an easy way to do it, but so far the easy way has escaped me... Please sign in to reply. Reply as... Cancel
David H Nebinger Laurent REMY 4 Years Ago The tool is solid, but it is not a code analysis tool. It really doesn't know what class changes have gone on in a package from build to build and won't know what the versions should be. It also wouldn't be able to distinguish between a minor version bump and a major version bump... I admit that I am terrible at package versioning. I religiously maintain javadocs on the classes and methods that I write, but I will totally forget to go back and update the package versions... I wish there was an easy way to do it, but so far the easy way has escaped me... Please sign in to reply. Reply as... Cancel