Berico-Technologies/CLAVIN — pull request #44 by seanlavelle (2013-08-23 22:41:36+00:00)
Title: The version in master should be a SNAPSHOT

When I clone Clavin locally and start changing things, my local builds overwrite the official latest release inside my local maven repo. This is kind of annoying, especially if I take a break and start building some other project which pulls clavin in as a dependency; I'll unexpectedly get my changed code when I wanted the official release! It happens because the version in the pom.xml in master is the same as the latest released version. The normal practice that I'm familiar with is for master's version string to be the "next" version with -SNAPSHOT appended. If I want my other project to pull in my unfinished changes I can change its dependency to point to the SNAPSHOT version.

So right now the version in master should be 0.4.3-SNAPSHOT. Once it's time for the next release, that would change to 0.4.3 (or perhaps 0.5.0, or whatever), the git tag for the release would have that final version number in it, and then the master branch would be updated to say 0.4.4-SNAPSHOT (or 0.5.1-SNAPSHOT)

I could just change the version number in the pom myself and then be careful not to commit my changes to pom.xml, but that's annoying :)