groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Champeau <cedric.champ...@gmail.com>
Subject Re: Gradle build updates
Date Mon, 11 Dec 2017 08:28:10 GMT
That's correct, the branch I have already does this.

2017-12-11 9:25 GMT+01:00 Paul King <paulk@asert.com.au>:

> The idea (once finished) is that you can still depend on a groovy-all
> dependency via Maven or Gradle and you'll automatically get the multiple
> required equivalent jars of the current single groovy-all jar.
>
> Cheers, Paul.
>
> On Mon, Dec 11, 2017 at 5:31 PM, Jim Northrop <
> james.b.northrop@googlemail.com> wrote:
>
>> Good morning Cedric
>> Wanted to ask if the removal of the jdk9 version of groovy-all jar will
>> also mean that all us stuck on jdk1.7 will not have newer versions of
>> groovy features? It would seem i would need to revise my gradles to include
>> needed dependencies that groovy-all used to have but not now?
>> Thanx Jim
>>
>> Sent from my iPad
>>
>> > On 11 Dec 2017, at 01:32, Daniel.Sun <sunlan@apache.org> wrote:
>> >
>> > Hi  Cédric,
>> >
>> >      It looks fine to me.
>> >
>> >      BTW,  the following commit will break the build(my bad...), please
>> > pull the latest code.
>> > https://github.com/melix/groovy-core/commit/fb00a0465e378bc9
>> 070f1e7dec4550fb778812ae
>> >
>> > Cheers,
>> > Daniel.Sun
>> >
>> >
>> >
>> > --
>> > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>>
>
>

Mime
View raw message