Hi, On Mon, 10 Dec 2018 at 15:19, Davide Giannella <[email protected]> wrote:
> Another point to keep in mind is the version number for diagnostic > builds[0]. So far we used the SVN revision which is unique and > incremental. This works perfectly in the OSGi world making sure any > diagnostic build will apply as planned. If moving to git purely, commits > are tracked as SHA and I don't think the incremental version aspect can > be enforced the same way. > > 0) http://jackrabbit.apache.org/oak/docs/diagnostic-builds.html > > We have to find a way to achieve the same when moving to git. Probably > by appending the full timestamp of the commit or some other form of time > related information. It probably won't be enough as if someone merge in > a commit "older" than the current HEAD, re-releasing a diagnostic build > will produce the same timestamp. > > Again, just quickly crushing my head on it, we could work out something > with the release-plugin skipping the tagging, but adding a commit every > time before we produce a diagnostic build. > > Something to be investigated. > Using a version composed by based version, timestamp and commit hash works well. The qualifier is compared lexicographically, so the timestamp would do the trick regardless of the commit hash. See this example [1] on Versionatorr. [1]: http://versionatorr.appspot.com/?a=1.0-20181210-79377d5aab231f27fa7e3dc7bdd0e828&b=1.0-20181209-8135fa0dc4bdb394f38afc1f084336a2
