On 04/25/2013 12:00 AM, Adam Murdoch wrote:
Looking at the code is probably the best option. There's no overview
documentation of the internals of Gradle at the moment, so the code is
the only documentation.
You're welcome to ask any questions you have about Gradle internals on
the dev list or on the forums and we'll try to help out.
Ok, thanks. I will do that.
Usually, if you let us know that you want to work on, we'll put together
a design document that will help you find your way through the
internals. So, no knowledge of the internals is required to get started
with contributions. Do you have some specific things you are interested
in working on?
For now I will first focus on my tool, maybe in June I will start
helping with Gradle.
http://forums.gradle.org/gradle/topics/make_the_gradle_wrapper_more_convenient_to_use_from_the_command_line
Looks interesting.
Thanks,
Patrick
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
