groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <pa...@asert.com.au>
Subject Re: Gradle build updates
Date Wed, 13 Dec 2017 06:35:44 GMT
Actually, it looks like you are still using skipIndy but why check for
java7Compatible when that is out minimum requirement anyway?

On Wed, Dec 13, 2017 at 4:21 PM, Paul King <paulk@asert.com.au> wrote:

> Should we just delete indy.gradle (obviously not in 2_4_X)? Otherwise the
> build fails for me when I used an old commandline with -PskipIndy=true.
>
> Cheers, Paul.
>
> On Mon, Dec 11, 2017 at 9:54 AM, C├ędric Champeau <
> cedric.champeau@gmail.com> wrote:
>
>> Hi folks,
>>
>> As promised I spent some time reworking the Gradle build. For those
>> interested, you can take a look at the progress checking out my branch [1].
>>
>> You'll notice that the build should be much faster [2], especially after
>> changes, and it now makes use of the build cache. I also got rid of the
>> crazy way to build the indy jars, it's now streamlined.
>>
>> I'm interested in feedback, since it's a potential breaking change. If
>> everything goes well, I will backport the changes to the 2.5/2.6 builds (so
>> please avoid changes there too).
>>
>> Thanks a lot,
>>
>> [1] https://github.com/melix/groovy-core/commits/cc/rebuild-gradle
>> [2] https://scans.gradle.com/s/msvk2xi57div2
>>
>
>

Mime
View raw message