Reacties op: From Maven to Gradle – part 1 http://www.beeworks.be/maven-to-gradle-part-1/ Wij bouwen websites, ontwikkelen software op maat en integreren bestaande toepassingen in websites en webapplicaties. Sat, 30 Jan 2010 23:39:35 +0100 http://wordpress.org/?v=2.8.4 hourly 1 Door: From Maven To Gradle - part 3 | BeeWorks http://www.beeworks.be/maven-to-gradle-part-1/comment-page-1/#comment-141 From Maven To Gradle - part 3 | BeeWorks Thu, 19 Nov 2009 18:54:41 +0000 http://www.beeworks.be/?p=285#comment-141 [...] the first 2 parts of this series on Gradle, we have migrated a simple project from Maven to Gradle, and [...] [...] the first 2 parts of this series on Gradle, we have migrated a simple project from Maven to Gradle, and [...]

]]> Door: Roger http://www.beeworks.be/maven-to-gradle-part-1/comment-page-1/#comment-134 Roger Fri, 13 Nov 2009 00:10:39 +0000 http://www.beeworks.be/?p=285#comment-134 The missing part from all these (for 0.8+ gradle) is how to exclude dependencies. All the old blog posts use addDepedency([], {exclude:}) or some other styntax which doesn't run anymore any ideas :)? The missing part from all these (for 0.8+ gradle) is how to exclude dependencies.

All the old blog posts use addDepedency([], {exclude:}) or some other styntax which doesn’t run anymore

any ideas :) ?

]]> Door: From Maven To Gradle - part 2 | BeeWorks http://www.beeworks.be/maven-to-gradle-part-1/comment-page-1/#comment-106 From Maven To Gradle - part 2 | BeeWorks Mon, 12 Oct 2009 13:25:08 +0000 http://www.beeworks.be/?p=285#comment-106 [...] the first part of this series, we discovered Gradle and tried to convert a simple Maven project, the domain model [...] [...] the first part of this series, we discovered Gradle and tried to convert a simple Maven project, the domain model [...]

]]> Door: Jason Porter http://www.beeworks.be/maven-to-gradle-part-1/comment-page-1/#comment-105 Jason Porter Sat, 10 Oct 2009 20:29:31 +0000 http://www.beeworks.be/?p=285#comment-105 Adding your blog post to the External Resources on the Gradle wiki: http://docs.codehaus.org/display/GRADLE/External+Resources Adding your blog post to the External Resources on the Gradle wiki: http://docs.codehaus.org/display/GRADLE/External+Resources

]]> Door: Peter http://www.beeworks.be/maven-to-gradle-part-1/comment-page-1/#comment-103 Peter Sat, 10 Oct 2009 15:01:41 +0000 http://www.beeworks.be/?p=285#comment-103 This is awesome. The time you wrote this is perfect for me. I have a hate-love relationship to maven, so I hope I can now switch to sth. better with my timefinder.de project. Thanks! > Gradle is the first real contender I’ve seen There is also buildr. Check out this picture: http://karussell.wordpress.com/2009/09/29/evolution-of-build-systems/ This is awesome. The time you wrote this is perfect for me.
I have a hate-love relationship to maven, so I hope I can now switch to sth. better with my timefinder.de project.

Thanks!

> Gradle is the first real contender I’ve seen

There is also buildr. Check out this picture:
http://karussell.wordpress.com/2009/09/29/evolution-of-build-systems/

]]> Door: Brian http://www.beeworks.be/maven-to-gradle-part-1/comment-page-1/#comment-102 Brian Fri, 09 Oct 2009 01:42:42 +0000 http://www.beeworks.be/?p=285#comment-102 Great write-up man. Totally breaks down the barrier to entry for Gradle for people working with Maven, especially when working with the Ivy DSL they provide. I haven't run into this as much with Java, but when working with Maven and other languages (i.e. - Flex), it's usually a train wreck. If you can't find a plugin to do what you want, you end up doing something similar to what you had to do for Hibernate, and write your own plugin. The beauty of Ant was that I could tackle those one-offs in my build script without having to construct infrastructure to support it (and the ant-run plugin Maven doesn't count :) ). Maven still has me locked in because of three things, dependency management, pom inheritance, and multi-module projects. Gradle is the first real contender I've seen that may offer a flexible enough solution to getting rid of the pain I experience with Maven. Looking forward to the 2nd post. Great write-up man. Totally breaks down the barrier to entry for Gradle for people working with Maven, especially when working with the Ivy DSL they provide. I haven’t run into this as much with Java, but when working with Maven and other languages (i.e. – Flex), it’s usually a train wreck. If you can’t find a plugin to do what you want, you end up doing something similar to what you had to do for Hibernate, and write your own plugin. The beauty of Ant was that I could tackle those one-offs in my build script without having to construct infrastructure to support it (and the ant-run plugin Maven doesn’t count :) ). Maven still has me locked in because of three things, dependency management, pom inheritance, and multi-module projects. Gradle is the first real contender I’ve seen that may offer a flexible enough solution to getting rid of the pain I experience with Maven. Looking forward to the 2nd post.

]]> Door: Ray Wenderlich http://www.beeworks.be/maven-to-gradle-part-1/comment-page-1/#comment-101 Ray Wenderlich Thu, 08 Oct 2009 13:38:52 +0000 http://www.beeworks.be/?p=285#comment-101 Thanks for the heads up on this. I too had some issues with Maven so I'll have to check this out. Thanks for the heads up on this. I too had some issues with Maven so I’ll have to check this out.

]]>