Hi Adam,
On Jul 17, 2008, at 12:48 AM, Adam Murdoch wrote:
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?)
In src/test/groovy are all the unit tests. Please set the following
system properties to run them:
-ea -Dgradle.home=roadToNowhere -Xmx512M
Than there are integration tests executed by the build. You can run
them with: gradle integTest
As trunk is only buildable with a snapshot version you might use the
gradle wrapper to build trunk, which means: ./gradlew integTest
You can also build trunk with trunk from your IDE.
- 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.
The core is everything except the DSL layer. As we are in the midst
of a refactoring from Groovy to Java this layer isn't yet
architecturally as separated as it should be. More or less everything
except the DefaultProject, DefaultTask and the org.gradle.groovy
package should be in Java.
- Does anything need to be sent to the dev mailing list before/
after making a patch letting people know what and why?
Honestly, I don't know.There is no process for this yet. The whole
approach how to coordinate and sustain team work needs to be
established. This is very important and I'm grateful that you are
pushing this topic.
I try to contribute some more stuff to the Wiki tomorrow.
Cheers,
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
