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 beig the default
bye Jochen
On 30.05.2017 23:48, Mario Garcia wrote:
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 by default
Is that correct ?
Mario
2017-05-30 17:24 GMT+02:00 Daniel Sun <realblue...@hotmail.com
<mailto:realblue...@hotmail.com>>:
> 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
<http://groovy.329449.n5.nabble.com/Indy-vs-default-build-tp5741393p5741420.html>
Sent from the Groovy Dev mailing list archive at Nabble.com.
