a note regarding net.shibboleth:parent-v3:2

[Tom Zeller]

I tagged and deployed (released) parent-v3 twice last night, because
after the first release I realized that the parent declared managed
dependencies which were snapshot versions, because they were children
of the parent.

I need to reflect and read a bit before updating the wiki.

The method I used was clumsy. Basically, the first step in the release
process is to release a parent which is incorrect because it declares
managed dependencies which do not exist, because the parent needs to
be released before the child dependencies can be.

Last night's released versions are :

net.shibboleth:parent-v3:2
net.shibboleth:java-support:2.0.1
net.shibboleth:spring-extensions:1.1.0

As a comment, I felt like I was loosing svn history by manually
manipulating a working copy to create a tag. For example, in Eclipse
if I right-click Team -> Show History on parent-v3 trunk, I do not see
any commit messages corresponding to the tag. Maybe not a big deal or
by design, but it seems to make history less linear.