Bug: Version number and git tag/hash not embedded in source release

[rleigh]

To remove the reliance upon git for versioning in the openmicroscopy build, the metadata retrieved from git must be embedded in the source release to allow building without the need for git. This must allow for building from a release zip/tar file without the presence of a git program or .git directory.

Examples:
​https://bitbucket.org/rleigh-debian/schroot-dist/src/2916b056f479885c331fad042041583884e5a797/VERSION?at=distribution-1.7
​https://bitbucket.org/rleigh-debian/schroot-dist/src/2916b056f479885c331fad042041583884e5a797/cmake/GitVersion.cmake?at=distribution-1.7

created using
​https://bitbucket.org/rleigh-debian/schroot-dist/src/2916b056f479885c331fad042041583884e5a797/cmake/GitRelease.cmake?at=distribution-1.7

The requirement is that the needed metadata be placed in a file which can be sourced and used to set the appropriate properties/variables for ant, maven and cmake. Where the systems are not compatible, it's possible to create different files for the different build systems, as illustrated above. It would be best if the same strategy could be used for both bioformats and openmicroscopy. In the above example, the information is derived from the git tag and its referenced commit.

The behaviour for the build systems to follow is to source the file if present, otherwise fall back to using git. This file will never be present in a git working tree.

At a minimum, this must include:

• the release date
• the release tag/commit (tag preferred; commit if untagged)
• the release version number

[jburel]

Moving to OMER0 5

[jburel]

Referencing ticket #11593 has changed sprint.

[rleigh]

Fixed in ​https://github.com/openmicroscopy/openmicroscopy/pull/1712