I haven't taken a serious look at Gaddle's design, but if we take out individual features (which may evolve differently on both sides), I would think the main deciding factor is your desire to work with either Ruby or Groovy.
On bigger projects, it's likely that you'll either want to extend the build tool or find issues (bugs or otherwise) and at that point, your comfort level with the language itself becomes quite important if you need to dig into the source or debug what's happening. One particular thing I enjoy about Ruby is the "Ruby is Unix" mentality where you can (more) easily interface with other native *nix tools, use fork() and such. If your approach is more towards abstracting away the operating system, and/or if all your libraries and tools are JVM-based, then this aspect may not carry as much weight. (Example: Buildr calls 'svn' or 'git' directly instead of using equivalent Java libraries) alex On Sun, Nov 1, 2009 at 9:11 AM, Sten Roger Sandvik <[email protected]> wrote: > Hi. > > I am a heavy Maven 2 user but lately I have been really tired of it. Been > looking at both buildr and gradle for some time now. Tried both buildr and > gradle in some real world settings. Right now I am favouring buildr since > it > gives me a good feeling to have control over my build. But I am worrying > about the community. Seems that the gradle community is bigger and more > active than buildr. That is just my feeling. > > In my build I have the need of building jars, wars and osgi modules. Could > someone give me a nice overview of pros/cons about buildr vs gradle? > > BR, > Sten Roger Sandvik >
