Hans Dockter wrote:
- I couldn't find anything much on the web site about contributing to
the project, eg how to provide patches, which jvms are we targeting,
testing, tracking in jira, etc
Good points. I gonna put them in the developer wiki soon. But I will
also answer some of them directly :)
Patches via Jira Issue and attachements
JVMs: 1.5 (We have started using the retrotranslator to produce an
additional JDK 1.4 compatible version. But there are still some
unsolved problems. )
Testing: JUnit 4.0 + JMock 2
Tracking in Jira? Do you mean svn tracking?
No, I just meant, do we track patches using Jira issues - which it looks
like we do
We are in the midst of refactoring our core from Groovy to Java. Any
contributions to the core should be in Java therefore.
I've added a page to the developer wiki with this detail in it. The
page needs someone to check it, as I just made up some of the details
(being a newcomer here, I don't know how things are done in gradle-land).
http://docs.codehaus.org/display/GRADLE/How+to+contribute+a+patch+to+Gradle
Some questions:
- How do you know if you've broken anything when you change stuff? (ie
which tests do I run, and how do I do so?)
- How do you decide what counts as the 'core', and therefore needs to be
implemented in java, and what does not count as 'core', and therefore
can be (must be?) implemented in groovy.
- Does anything need to be sent to the dev mailing list before/after
making a patch letting people know what and why?
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
