+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 an easy switch but it might involve a little more tweaking that will end up being thrown away, in which case I would head for "indy only". Similarly, if we change groovysh, groovyConsole etc., if an easy flip isn't possible, I would be inclined to just go full indy. As for the build changes, I would be inclined to head straight to indy only there too. My other main concern would be with different tools having different states for "indy by default". But that is something which I guess isn't too hard to manage. Cheers, Paul. On Thu, Feb 27, 2020 at 6:56 AM Daniel.Sun <sun...@apache.org> wrote: > 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 >
