We're currently using Maven for a lot of our projects at JBoss and I've been
researching Gradle a bit to see if it can solve some problems in our builds. I
set up one of our simple builds to use Gradle just to check it's performance vs.
Maven, and I was kind of surprised to see that Gradle seemed somewhat slower for
the build.
The project is a basic java/jar project and I am using the gradle "java" plugin.
In Maven this is equivalent to a "jar" packaging. So running a clean build
gradle clean libs ~ 12s
mvn clean package ~ 8s
gradle libs ~ 10 - 20s (This one varied quite a bit while testing)
mvn package ~ 5s
Maven builds seem significantly slower in general than Ant builds, so I was
hoping that Gradle would be somewhere in between. So anyway, my question is
mainly (1) whether performance is a known problem with Gradle and it's being
worked on, (2) maybe Gradle just has a slow startup time and with bigger
projects it's not an issue, (3) maybe I'm doing/not doing something that is
making the build slower.
I obviously didn't do any detailed test, but I did notice that in my small build
the steps that seem to take the most time are the initial startup, the test
task, and the jar task.
How do I tell Gradle to fork once for the tests instead of the default per test
forking? Also I remember reading something in the user guide about pre
compiling the build script, how do I do that?
Thanks much!
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
