posted 11 years ago
In purely ideological terms, a tag applies to a specific version and should therefore be forever tied to that version, because that's the whole point of version control - committing versions to the archive and thereby "setting them in stone". And Eclipse encourages that practice. Unlike CVS, where a tag was a mutable label and you could have more than one of them, in SVN, the tag is the name of the actual archive itself.
This is different from a branch, which is a work in progress and therefore allowed to change (accumulate new versions).
However, in SVN terms, the whole branch/tag/trunk thing isn't an architectural component of SVN, just a convention on how to manage things, so while Eclipse may object to updating a tag, SVN doesn't care.
Note, however, that copies and commits are done differentially, so where you post your "tagged version" is really immaterial in terms of SVN server storage resources. So whatever actual path - branch, tag, trunk, or whatever, SVN won't care about anything except getting the path of the commit right.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.