Hey Adam,

Thank you so much for your proposal! We have reviewed your submission and so far all the mentors have given it a high rating :)

I took a look at your prototype groovy-manager project, which looks very interesting. You are doing source parsing for groovy, which is pretty challenging.

While writing a parser from scratch can be a thrilling challenge, I have to say that it can be quite a burden! We started writing our own Java-parser for Forge, but quickly came to find that even parsing a type-safe language is incredibly difficult.

We ended up using the Eclipse JDT as a base implementation for our JavaParser.

Have you looked for any Groovy parsers that may already exist today? This would give you a quick boost when working on this project. It may be the case that the parser would require some usability improvements to make integration with Forge simpler, and simpler for plugin devs, but I think it is safe to say that a search for existing parsers is warranted.

If a suitable parser can be found, I would suggest that we revise your proposal to allow for several weeks to become familiar with that parser, and then allocate the rest of the time to actually working with it to implement the gradle support.

I'd suggest starting here, with the Groovy Eclipse Plugin - they almost certainly already support groovy syntax: http://groovy.codehaus.org/Eclipse+Plugin#EclipsePlugin-KeyFeatures

The problem with writing your own parser is that you have to maintain it :) Better to delegate.



On Sun, May 5, 2013 at 5:05 PM, Adam Wyłuda <adamwyl92@gmail.com> wrote:
Hello JBoss community,
This year I want to participate in an OS project and GSoC gives me great opportunity to do so.
Here is my idea as GSoC 2013 proposal: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/adamw/1
I'd be very happy to hear your opinions (I hope it's not too late).

forge-dev mailing list

Lincoln Baxter, III
"Simpler is better."