A
Andrew Arrow
Hello, I come from the Java world and really enjoyed using maven:
http://maven.apache.org/
The big pluses maven gave us were:
1. Easily maintain version numbers for projects.
Maven would start you at 1.0 and after each release bump your project to
1.1, 1.2 etc. It would also tag the version in SVN for you, and make
your current working version 1.2-SNAPSHOT until your next 1.3 release.
2. Central repository for all projects with dependency management.
You can just say I need projectX version 1.2 and it'll magically get
that for you AND get projectY version 1.1 because it knowns projectX
depends on projectY.
Both these features made it very easy to break any large project into
many smaller projects. The more smaller projects you have with well
defined API's make everything better. One team can work on projectA,
while another works on projectB. ProjectA guys will often say, "Hey I
need this from ProjectB..." and in a few minutes there's a new version
of B ready on the central repository.
I'm just learning Rails, but so far I have a huge rails project with
many controllers, many models, many plugins, a large lib folder, etc.
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.
Thanks.
http://maven.apache.org/
The big pluses maven gave us were:
1. Easily maintain version numbers for projects.
Maven would start you at 1.0 and after each release bump your project to
1.1, 1.2 etc. It would also tag the version in SVN for you, and make
your current working version 1.2-SNAPSHOT until your next 1.3 release.
2. Central repository for all projects with dependency management.
You can just say I need projectX version 1.2 and it'll magically get
that for you AND get projectY version 1.1 because it knowns projectX
depends on projectY.
Both these features made it very easy to break any large project into
many smaller projects. The more smaller projects you have with well
defined API's make everything better. One team can work on projectA,
while another works on projectB. ProjectA guys will often say, "Hey I
need this from ProjectB..." and in a few minutes there's a new version
of B ready on the central repository.
I'm just learning Rails, but so far I have a huge rails project with
many controllers, many models, many plugins, a large lib folder, etc.
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.
Thanks.