Another way I've seen done is to execute "git rev-parse HEAD" in a custom
Gradle task and dump the result into a resource file (similar to how Groovy
provides the version info today). But using Grgit/JGit is better since it
will work without the assumption that git is on your path.
-Keegan
On Tu
On 11.10.2016 11:56, Paul King wrote:
Russel, do you know a project with a similar build setup already doing
this so we can 'borrow' their approach?
On Sun, Oct 9, 2016 at 2:58 PM, Russel Winder wrote:
Would it be possible to include the Git identifier of the changeset
being compiled in the
Russel, do you know a project with a similar build setup already doing
this so we can 'borrow' their approach?
On Sun, Oct 9, 2016 at 2:58 PM, Russel Winder wrote:
> Would it be possible to include the Git identifier of the changeset
> being compiled in the version number displayed by groovy -ver
Would it be possible to include the Git identifier of the changeset
being compiled in the version number displayed by groovy -version for
Groovy build from master?
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200 v
