Cedric's comment linked at the bottom of that post is excellent in describing the issue. The gradle DSL has been designed in a way that is hard to support by IDEs, partly because groovy made that so easy.
And the same might be true about other popular groovy frameworks. Having to support plugins for each IDE for each framework specific DSL is not viable. If there were a lesson to be learned here for a vastly different groovy 3, it is hard to imagine that in practice those lessons could be applied. On Monday, May 23, 2016, Schalk Cronjé <[email protected]> wrote: > As a follow-up to Dan Woods post regarding reactions of the ApacheGroovy > community to the recent announcement of Kotlin support in Gradle, I had > posted the following > > > http://delivervalue.blogspot.co.uk/2016/05/about-gradle-kotlin-and-inner-fear.html > > in the hope that it will elicit more conversation regarding the state of > the Groovy nation. > > -- > Schalk W. Cronjé > Twitter / Ello / Toeter : @ysb33r > >
