On 2/23/07, Andrew Arrow <andrew / geni.com> wrote:
> Is there a good maven for ruby yet?  Is capistrano the answer?  I want
> to split my large rails project into like 20 separate projects and then
> have a small skeleton rails app that just pulls the 20 together.

Fortunately, Ruby doesn't need something as overengineered as Maven.
If you need to subdivide your projects, just do so. Make them Ruby
libraries that you can install yourself. Divide them logically; when
you find out that it doesn't work, join them back together as you need
to. Use the advantages of your source control tool without being tied
to the concept of something like Maven.

Capistrano is a deployment tool. Rake is a build tool. There's at
least three cruise-control-like solutions. If you decide that, even
internally, hoe gives you amazing tools that you don't have to use
entirely (you can use hoe to test each component, package it as a gem,
and then extend it to copy it to your deployment server instead of
uploading it to RubyForge).

And ... do you really need a "huge" rails project? If your project can
be divided into twenty sub-projects, shouldn't you be doing it
*properly* (making proper libs, etc.) and not depending on something
like Maven to do it for you?

-austin
-- 
Austin Ziegler * halostatue / gmail.com * http://www.halostatue.ca/
               * austin / halostatue.ca * http://www.halostatue.ca/feed/
               * austin / zieglers.ca