Clean up version number handling

dCache uses an intricate web of reflection code to obtain
version number information of various components. It also
relies on CVS/SVN revision number substitution, which will
be a problem when we move to other source code management
systems.

This patch injects branch and revision number information
into the JAR manifest files (which already contain the
build time and version number). The patch replaces all
version handling code in dCache, which now relies solely
on the information found in the manifest files.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5256/
(cherry picked from commit 4ab93514f346404a1fb5bf1dd024cc978284a381)
Fix 'dcache version' regression

We recently decoupled version number handling from SVN. That change introduced
a regression in that the 'dcache version' command no longer prints the
version number of dCache.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Christian Bernardt <christian.bernardt@desy.de>
Patch: http://rb.dcache.org/r/5445/
(cherry picked from commit a1c116fbbcbb5ea5f7f2ed0e26a021a24810e9f5)
Remove version number handling for SVN

Since we no longer use SVN, we can simplify our Maven
project by not supporting SVN revision numbers.

Target: trunk
Require-notes: no
Require-book: no
Acked-by: Paul Millar <paul.millar@desy.de>
Patch: http://rb.dcache.org/r/5532/
(cherry picked from commit c9fc6b93e5515e440bf37f2c9c4ae80cf4554212)
Merge pull request #20 from gbehrmann/fix/2.5/version-number

Make version numbers and revisions work with git