> -web pages and people state that gradle is prohibitively slow. I find that > hard to believe but a lot of people seems to reiterate it, >
Old versions yes, but newer versions allow you to start a Gradle deamon as part of the first build. That deamon then speeds up follow up builds. > -Will I be able to maintain my own project structure (src/) or I will have > to succumb to a ten level directory depth (prj/main/src/java/) like my life > is not complicated enough? It's absolutely no fun to rearrange several > projects just for somebody else shake. Maven looks like such an XML > straitjacket that I am not sure breathing is allowed without issuing $mvn > breathe first. > Of course! Gradle has lots of conventions but you can change them all with a few lines. > -How about IDE integration? I don't want to maintain the same settings > (classpath, included projects) twice. Right now a custom script of mine > parses .classpath eclipse files and create ant build files. Not great but > it was beating the competition when maven was introducing itself into the > world (~2009). How gradle/maven handles that? Should I use eclipse plugins? > What about other IDE? > There are IDE plugins for Eclipse. There was a good one maintained by the spring guys but now gradle has its own official eclipse plugin: https://gradle.org/eclipse . IntelliJ brings its own Gradle integration as part of IntelliJ. If nothing helps Gradle has a plugin to generate project files for Eclipse / IntelliJ and allows you to customize these project files. That way you can manually configure Eclipse / IntelliJ in case automatic import does not work for your project because its too complicated to setup (like GWT for example) > -Surely gradle looks saner. Is it mature enough? Or it will start the "I > can't let you do that Dave" on me? Will it try to download the Internet > like maven? > Gradle build scripts are Groovy Scripts. So while the syntax of Gradle scripts look like a DSL its actually script code. You can even write Java code inside the build files. So you can do everything you want with Gradle. Gradle only downloads itself if needed (you have a generated shell script in your project that people can use even if they have not gradle installed), the plugins you have defined in your build file and the dependencies you need for your project. IMHO Maven was "good" 10 years ago, but today you better stick with Gradle. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
