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
whoops, obviously wrong mailing list. My appologies
Regards,
Jeff Adamson
From: Jeff Adamson/Cleveland/IBM@IBMUS
To: dev@groovy.apache.org
Date: 10/11/2016 09:18 AM
Subject:ant wrapper script testing
I have been doing some work on trying to correct errors in the ant shell
scr
I have been doing some work on trying to correct errors in the ant shell
script with how special characters and whitespace and handled in arguments.
I have a scratch branch in github. I do forced pushes as I clean it up and
try new things, so beware forking.
https://github.com/jwadamson/ant-1/tr
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
On 11.10.2016 06:14, 孙 岚 wrote:
Hi dev list,
Are there any compiler optimizations in Groovy? e.g. Tail
Recursion, Loop Unrolling, etc.
If no compiler optimizations done, how about providing some AST
Transformation or even adding a compilation phase named optimization?
The optimiza
