bundler, warbler, and :git gems

[tom_302]

Hello,

I'm trying to deploy a jruby/rails project that uses a forked version of rails from a local git repo. My Gemfile includes the following line:

gem 'rails', :git => File.expand_path('../../rails', __FILE__), :branch => '3-1-backported

I run jruby -S bundle install --deployment --binstubs --standalone && jruby -S bundle exec rake war to create my deployment war. However, bundler says rails is not checked out and wants to install it. In the war, I have WEB-INF/gems/gems (normal gems) and WEB-INF/gems/bundler/gems (git-based gems).

I'm curious why bundler handles :git-based gems differently from regular gem sources (for deployment mode). Shouldn't bundler (or warbler) simply pre-build the :git based gems and then include them like normal gems?

Thanks in advance.

[Andre Arko]

Git gems are, by definition, simply git repos. There is no "standard" Rubygems build system used by all gems, so there is no way to build git gems into .gem files. Checking out the git repo and making sure that lib/ ends up in the load path and bin/ ends up in the regular path is the closest we can get.

I've never used Warbler, so questions that are specific to it should probably be asked on its mailing list.

> --
> You received this message because you are subscribed to the Google Groups "ruby-bundler" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/ruby-bundler/-/80YwVJIQ3l0J.
> To post to this group, send email to ruby-b...@googlegroups.com.
> To unsubscribe from this group, send email to ruby-bundler...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ruby-bundler?hl=en.
>