Rails Ruby on Rails

I am working on a plugin for maven (a java build and project management tool) to offer ruby, gem, rspec and rails support. the main difficulty with rails3 is that bundler and the maven plugin overlap quite a bit on functional level. so I was looking for ways let bundler and maven coexists without favoring one or the other.

the current approach is to patch the config/boot.rb in a way that is does allow to use Gemfile.maven as "Gemfile" (the patched file looks like this http://github.com/mkristian/jruby-maven-plugins/blob/next/rails3-ma.... so basically it obeys the environment variable BUNDLE_GEMFILE and uses it if set prior to setting the rails default.

with this patch one can take a newly created rails application and apply an maven archetype (like rails generators) to mavenize the application in a way that you can still use the rails application in the usual way as well use maven to run the webrick/mongrel server, to call generators or rake tasks or bundle the whole application into a war file for deployment.

so my aim is really to keep the rails application as it is and add a few files to use the very same with maven. but right now I need to patch the config/boot.rb to achieve this which is against the actual spirit.

so the attached patch does the same patch as maven does and I added an unit test which test most functionality. the patch is trivial but would let tools like maven to behave non invasive and maybe there are other usecases for more then one Gemfile (MRI versus JRuby when you need to lock down you dependencies, etc)