On Sun, Jun 23, 2013 at 12:28 PM, Daniel Marcotte <dmarco...@gmail.com> wrote:
> Any thoughts on migrating to Gradle rather than Maven? This should give
> better tools for capturing the complexity of the existing ant build while
> still having all the benefits you're after from Maven.
Gradle is a great tool, but there's too many reasons not to use it.
* Gradle (+ Groovy) is a *big* dependency (as in size) to require for
building JRuby.
* Gradle does not appear to have a standard package on most Linuxes,
homebrew, etc. Maven has standard packages on pretty much every system
out there.
* Maven is pre-installed by most Java development environments.
* Maven is supported by all flavors of IDE and editor.
* Maven can call out to Ant (or better yet, Rake) for anything
procedural we need it to do.
* We have been moving more and more dev-time logic out of Ant and into
Rake. Introducing Groovy code into our codebase would be a step
backward.
* There are Ruby/JRuby/Rake plugins for Maven.
* It just feels wrong to me to build JRuby with Groovy+Gradle when we
have Ruby+Rake (or Buildr, but I don't know if it's still maintained).
I see Maven primarily handling building JRuby itself (jruby.jar,
jruby-complete.jar) and distributing the Maven artifacts, deferring to
Rake for most other stuff (test runs, downloadable archives, etc). In
other words, mostly for bootstrapping JRuby (so we can do everything
else in Ruby) and publishing artifacts. Gradle doesn't gain us
anything over Rake in that case.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
