<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
BTW, I gave push permission for your user "adamwy" in Github to the
repository <a class="moz-txt-link-freetext" href="https://github.com/forge/addon-gradle">https://github.com/forge/addon-gradle</a><br>
<br>
Forge ahead !! <br>
<br>
<br>
<div class="moz-cite-prefix">On 06/04/2013 09:56 AM, Adam Wyłuda
wrote:<br>
</div>
<blockquote
cite="mid:CAOzHfokvnFrbDdLLevNVDseHVv1V=q1+3a+qGEnRFk3rpsywAA@mail.gmail.com"
type="cite">Hi!
<div>This year I have been chosen as a GSoC participator and I'd
like to say that I'm very happy to join Forge team this summer
(and I hope for longer! :)).</div>
<div><br>
</div>
<div>My project is called "Support for the Gradle build system as
a plugin for Forge" but it actually should be named an addon
instead of plugin as I'm targeting Forge 2 API.</div>
<div><br>
</div>
<div>I have already posted it some time ago, but for those who are
interested and have not seen it, there is a link to my proposal:</div>
<div><a moz-do-not-send="true"
href="https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/adamw/1">https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/adamw/1</a></div>
<div><br>
</div>
<div>There is a rough plan of what I want to do:<br>
- find and wrap the best possible Groovy parser implementation
to create a JavaParser-like util</div>
<div>- study Forge Maven addon implementation, to name things
which must be obtained from the Gradle build script that are
necessary to work effectively with the Gradle projects (like
dependencies, source code location, etc.)</div>
<div>- get familiar with Gradle tooling API and use it along with
GroovyParser to implement Forge Gradle project addon</div>
<div><br>
</div>
<div>The most complex task for this project is probably the
GroovyParser. If it will seem to take longer than expected (with
the risk that I won't be able to complete project in time),
there is an alternative solution. I could use the simplest
approach, i.e. use a tool which will traverse through Groovy
script abstract syntax tree and find a place to put a piece of
code. I have already implemented this (link in my proposal), and
it seems to be sufficient enough to use it in parts of
GradleProject which require Gradle script modification (like
adding a dependency).</div>
<div><br>
</div>
<div>During the summer, I plan to work during the working days
from about 12PM to 8PM at GMT+1. Lincoln already created a
repository for me on GitHub, so you can track my progress at:</div>
<div><a moz-do-not-send="true"
href="https://github.com/forge/addon-gradle">https://github.com/forge/addon-gradle</a></div>
<div><br>
</div>
<div>I hope I gave enough information about my work, and I also
hope that I won't disappoint you during this summer :).</div>
<div><br>
</div>
<div>~ Adam</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
forge-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a></pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<b>George Gastaldi</b> | <i>Senior Software Engineer</i> <br>
JBoss Forge Team<br>
Red Hat<br>
</div>
</body>
</html>