<div dir="ltr">Yes. I agree100%, but to modify the gradle build file, we will need to be able to parse and understand the source. It would be nice to include a Groovy Parser in Forge anyway! <div><br></div><div style>Gradle definitely has a lot of tooling issues to overcome.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 7, 2013 at 8:08 AM, Max Rydahl Andersen <span dir="ltr"><<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">AFAIK, gradle team tells tooling that want to understand gradle build files<br>
is to use and *run* gradle-tooling-api to parse it. Don't try parse it.<br>
<br>
I believe eclipse plugin uses that.<br>
<br>
See <a href="http://www.gradle.org/docs/current/userguide/embedding.html" target="_blank">http://www.gradle.org/docs/current/userguide/embedding.html</a><br>
<br>
(it's one of the reasons I'm not really happy about gradle since its<br>
dog start/slow to run on large set of projects - they keep saying that<br>
will improve though...)<br>
<span class="HOEnZb"><font color="#888888"><br>
/max<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Mon, May 06, 2013 at 07:27:20PM -0400, Lincoln Baxter, III wrote:<br>
>Hey Adam,<br>
><br>
>Thank you so much for your proposal! We have reviewed your submission and<br>
>so far all the mentors have given it a high rating :)<br>
><br>
>I took a look at your prototype groovy-manager project, which looks very<br>
>interesting. You are doing source parsing for groovy, which is pretty<br>
>challenging.<br>
><br>
>While writing a parser from scratch can be a thrilling challenge, I have to<br>
>say that it can be quite a burden! We started writing our own Java-parser<br>
>for Forge, but quickly came to find that even parsing a type-safe language<br>
>is incredibly difficult.<br>
><br>
>We ended up using the Eclipse JDT as a base implementation for our<br>
>JavaParser.<br>
><br>
>Have you looked for any Groovy parsers that may already exist today? This<br>
>would give you a quick boost when working on this project. It may be the<br>
>case that the parser would require some usability improvements to make<br>
>integration with Forge simpler, and simpler for plugin devs, but I think it<br>
>is safe to say that a search for existing parsers is warranted.<br>
><br>
>If a suitable parser can be found, I would suggest that we revise your<br>
>proposal to allow for several weeks to become familiar with that parser,<br>
>and then allocate the rest of the time to actually working with it to<br>
>implement the gradle support.<br>
><br>
>I'd suggest starting here, with the Groovy Eclipse Plugin - they almost<br>
>certainly already support groovy syntax:<br>
><a href="http://groovy.codehaus.org/Eclipse+Plugin#EclipsePlugin-KeyFeatures" target="_blank">http://groovy.codehaus.org/Eclipse+Plugin#EclipsePlugin-KeyFeatures</a><br>
><br>
>The problem with writing your own parser is that you have to maintain it :)<br>
>Better to delegate.<br>
><br>
>~Lincoln<br>
><br>
><br>
><br>
><br>
>On Sun, May 5, 2013 at 5:05 PM, Adam Wyłuda <<a href="mailto:adamwyl92@gmail.com">adamwyl92@gmail.com</a>> wrote:<br>
><br>
>> Hello JBoss community,<br>
>> This year I want to participate in an OS project and GSoC gives me great<br>
>> opportunity to do so.<br>
>> Here is my idea as GSoC 2013 proposal:<br>
>> <a href="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/adamw/1" target="_blank">http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/adamw/1</a><br>
>> I'd be very happy to hear your opinions (I hope it's not too late).<br>
>><br>
>> _______________________________________________<br>
>> forge-dev mailing list<br>
>> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
>><br>
><br>
><br>
><br>
>--<br>
>Lincoln Baxter, III<br>
><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
>"Simpler is better."<br>
<br>
>_______________________________________________<br>
>forge-dev mailing list<br>
><a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
><a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br>
<a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."
</div>