Does indy by default mean
1. only generate one set of groovy-* artifacts where any .groovy source
files in the Groovy source itself are compiled using indy (no more separate
indy jars)
or
2. continue to have two sets of artifacts where the indy set would go in
lib/ by default and -noindy jars
in my opinion if JDK8 is the minimum requirement we can switch to indy
as default, while keeping the old call site caching as is.
It is more that in the long term we want to get rid of code that has no
future and all that. But I see no hard requirement to do those things
just because of indy b
If I didn't get it wrong, there is a possibility to have indy as a default
only if:
1. Callsite caching is rewritten to work with indy/no indy
2. We keep binary compatibility Groovy 3 / JDK7 until Gradle moves to
Groovy 3
3. Then we will be able to move to Groovy with JDK8 and set Indy
> I don't think it would be good if gradle stayed on Groovy 2.x. That would
counter the acceptance of Groovy 3
Agreed.
Cheers,
Daniel.Sun
--
View this message in context:
http://groovy.329449.n5.nabble.com/Indy-vs-default-build-tp5741393p5741420.html
Sent from the Groovy Dev mailing list arc
