I suspect a deep knowledge of the inner workings of Eclipse would be required. You could always take a look at the code on GitHub [1] and see if you can make sense of it. Although, it may not be as dead as we have been led to believe (I personally use IntelliJ) as it looks like that latest SNAPSHOT was released Mar 4, 2016.
Cheers, Keith REFERENCES 1. https://github.com/groovy/groovy-eclipse <https://github.com/groovy/groovy-eclipse> > On May 25, 2016, at 7:22 PM, Balachandran Sivakumar <benignb...@gmail.com> > wrote: > > Hi, > > On Mon, May 23, 2016 at 10:02 PM, Balachandran Sivakumar > <benignb...@gmail.com <mailto:benignb...@gmail.com>> wrote: > Hi Cedric, > > On Mon, May 23, 2016 at 5:27 PM, Cédric Champeau <cedric.champ...@gmail.com > <mailto:cedric.champ...@gmail.com>> wrote: > there's absolutely no need for an external DSL descriptor: all the constructs > of the language, like extension methods or static builders are first class > language features. The issue is, IDE support for Groovy is lacking (Groovy > Eclipse is dead, IntelliJ needs to know specifics of static Gradle/Groovy > scripts, ...) > > If we have to resurrect it, what would it take ? I mean, what skill > set/knowledge should someone have to work on it and resurrect it ? Also, can > someone here help with that effort ? Thanks > > > Can someone please help with this ? What would it take for someone with > reasonable Groovy/Java knowledge to pick up Goovy Eclipse and maintain it ? > Thanks > > -- > Thank you > Balachandran Sivakumar > ------------------------------ Research Associate Department of Computer Science Vassar College Poughkeepsie, NY
