Hi, Gradle is a build system, similar to Maven. I noticed that there's a "gradle init" command which automatically turns your Maven project into a Gradle project. As our Maven tests are quite slow, I've given it a try to see if Gradle is faster. The conversion didn't work 100% but issues could be worked around (see below). Here are the numbers for running the tests with Gradle:
gradle clean -> 0:08 (i.e. 8 seconds) gradle test -> 5:47 gradle test -> 0:14 (well, nothing has changed) now change the German grammar.xml gradle test -> 2:30 now change a Java file in languagetool-wikipedia gradle test -> 0:45 You can see here that gradle actually considers the dependencies, i.e. a change in a module will run all the module's tests and all the tests of the modules that depend on it. As a comparison, "mvn clean test" takes about 5 minutes on my computer. Conclusion? It's probably not worth switching to Gradle, as the full test build is even a bit slower than with Maven and one rarely needs to run a full test. If anybody here has an issue with Maven and the tests being slow, please see http://wiki.languagetool.org/maven-tips to make sure you use all the tricks that keep test times down. If someone actually wants to try, here are the things you need to do after "gradle init"'s incomplete conversion: http://stackoverflow.com/questions/5144325/gradle-test-dependency http://stackoverflow.com/questions/7459755/how-can-i-make-gradle-include-ftl-files-in-war-file Regards Daniel ------------------------------------------------------------------------------ _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
