Comments on: Ruby: A Better Build for Java http://labnotes.org/2006/12/30/ruby-a-better-build-for-java/ Sun, 15 Jan 2012 21:29:54 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Labnotes » Introducing Buildr, or how we cured our Maven blues http://labnotes.org/2006/12/30/ruby-a-better-build-for-java/comment-page-1/#comment-137828 Labnotes » Introducing Buildr, or how we cured our Maven blues Wed, 18 Apr 2007 18:54:42 +0000 http://blog.labnotes.org/2006/12/30/ruby-a-better-build-for-java/#comment-137828 [...] no secret I have a love/hate relationship with Maven 2.0. I hate it. And I love using it as an example of how [...] [...] no secret I have a love/hate relationship with Maven 2.0. I hate it. And I love using it as an example of how [...]

]]> By: Lee http://labnotes.org/2006/12/30/ruby-a-better-build-for-java/comment-page-1/#comment-137609 Lee Wed, 14 Feb 2007 12:53:14 +0000 http://blog.labnotes.org/2006/12/30/ruby-a-better-build-for-java/#comment-137609 I totally agree. In fact I wrote about my experiences on my blog. For me it boiled down to two fundamental things: 1. I want to have one repository (for example svn) and not two (svn and maven). 2. The rigidity of the build cycle. It just doesn't work on projects where you have several databases, webservices, teams, and continuous integration going on. A lot of time wasted trying to get Maven to stuff. I totally agree. In fact I wrote about my experiences on my blog. For me it boiled down to two fundamental things:

1. I want to have one repository (for example svn) and not two (svn and maven).

2. The rigidity of the build cycle. It just doesn’t work on projects where you have several databases, webservices, teams, and continuous integration going on. A lot of time wasted trying to get Maven to stuff.

]]>