version numbering inconsistency

[Ian Young]

The java-support module's most recent released version is 4.0.0, and the current POM is set to 5.0-SNAPSHOT on the assumption (I think) that the next release will make incompatible changes and be 5.0.0. I think this matches our versioning policy at https://wiki.shibboleth.net/confluence/display/DEV/Branches%2C+Tags%2C+and+Versions and is also happy-making for the "mvn versions:display-dependency-updates" command.

The spring-extensions module's most recent released version is 2.0.0, but the current POM is set to 2.0-SNAPSHOT. I think this is wrong, and should be either:

2.1-SNAPSHOT if we think the next release will be compatible, or

3.0-SNAPSHOT if we think the next release won't be compatible

With the current 2.0-SNAPSHOT value, the current snapshot looks like a precursor to the previous actual release, which causes "mvn versions:display-dependency-updates" to complain that a newer version is available.

Every time something like this happens, I find myself confused so I could be wrong about the above, but can I get confirmation that a version bump of one kind or another is required here?

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5943 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20141007/7b4f1d78/attachment.bin