It is what we state in the roadmap (it was originally in the Groovy 3
roadmap but we ran out of time/resources):
http://groovy-lang.org/releasenotes/groovy-4.0.html
But agreed mg, we should make some more noise in user and dev mailing lists
at some point soon - possibly once we have done a little
It seems to me a clear "Groovy 4 will be indy only" message would enable
everyone who potentially had to make some adjustments, do some testing,
etc to set aside some time for this - and it has to happen at some point
anyway.
Cheers, mg
On 26/02/2020 23:55, Paul King wrote:
+1 to the idea of "
+1 to the idea of "enabling indy by default" but, since our aim is for
"indy only", I would be cautious of putting too much energy into steps that
will possibly end up being wasted work.
If our cli for the compiler already handles --indy=false (if we just flip
the default value), that would seem a
Hi Paul,
How about enabling indy by default in the 4.0 alpha release?
Cheers,
Daniel.Sun
-
Apache Groovy committer & PMC member
Blog: http://blog.sunlan.me
Twitter: @daniel_sun
--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
We weren't planning another 2.4 release but there is a significant bug in
2_4_X which impacts Spock users using special characters in their method
names, 2_5_X users are calling for partial JDK 14 support, and we already
have some fixes in the 3_0_X stream that would be good to get out soon. So
I t
