-
What is Groovy?
-
Groovy is a powerful high level language for the Java platform which compiles
down to Java bytecode.
Think of it as a Ruby or Python like language that is tightly integrated with
the Java platform - allowing you the same powerful and concise coding syntax as
Ruby or Pyton but allowing you to stay on the JVM and protect your investment in
J2SE, J2EE and all the plethora of great useful Java code out there.
-
What are the dependencies for Groovy?
-
As well as Java 1.4 and the Groovy jar we also depend at runtime on the ASM library
-
What is the licence for Groovy?
-
Groovy is open source using a BSD / Apache style licence
-
How can I contribute to Groovy?
-
There are many ways you can help and contribute to Groovy.
Please read the contributing guide
-
How do I build Groovy from the source code?
-
We use Maven as the build tool for Groovy.
From a source distribution, or CVS checkout
you need to install Maven as per the instructions on Maven's website.
Basically this involves setting the JAVA_HOME and MAVEN_HOME environment
variables and adding JAVA_HOME/bin and MAVEN_HOME/bin to your path.
Once you have installed Maven you can build Groovy and run all the unit tests
by typing the following in a command line shell
-
All the unit test cases take a while to run. Can I do a quicker build?
-
You can do a full clean binary build without running the unit tests via..
If you want to run all the unit test cases inside the same JVM, which saves quite a bit of time
although the output isn't as nice, you can use this command.
-
All the unit test cases take a while to run. Can I run just some of the tests?
-
Or to run a specific test case you can do
maven test:single -Dtestcase=CharsetToolkitTest
Where you pass in the name of a test case. If you want to run a single unit test case
written in Groovy in a slightly faster way you can try this...
maven groovy:test-single -Dtest=src/test/groovy/SomeTest.groovy
or to run tests matching a certain pattern...
maven test:match -Dtestmatch=Foo*Test.*
There is more details on unit testing groovy scripts here
-
I've just been given CVS commit access; what should I do now?
-
If you've just been given CVS commit access see if you can do a commit.
You'll need to do an SSH based CVS checkout. Once you've done this
you should be able to edit the project.xml file and change yourself
from being a committer to being a developer. Then try commit that
and see if it works.
If you need more help, please ask on IRC or email.
-
What are the development rules?
-
Please try and write unit test cases for all new features, patches or fixes.
Its considered very bad form to commit code that doesn't compile or breaks the unit tests.
We run a continuous integration build (using DamageControl) to ensure that the build in CVS
works and the tests pass.
Its useful to subscribe to all 3 mail lists, especially groovy-scm which shows all CVS commits
along with any continuous integration build failures and JIRA issue changes.
-
Where is the continuous integration build?
-
We run DamageControl at codehaus. If a build fails a nag mail is sent to the groovy-scm mail list.
You can watch DC do its stuff using your IRC client and joining
#damagecontrol.
You can also view the latest DC build logs
or see the test case results
-
How do I use codehaus's CVS?
-
Codehaus uses SSH for CVS access. So from the command line you'd type
Or if you're using eclipse you might find
this plugin
handy.
I use it with extssh2 and it works great!