Installed gems via 'bundle --deployment' are not picked up by TB about backstage

[tobias]

(commenting from the proper account)

Bundler is responsible for loading the gems from ./vendor/, and for some reason I disabled bundler back in April (eac19ae). A smarter man would have mentioned why in the commit message. I'll take a look and see if we can bring it back - the issue may have been the Gemfile.lock being too strict in relation to the dependencies that gem installs, but maybe we can work around that.

[davidglassborow]

That's great tobias. Give me a shout if I can help.

[tobias]

@davidglassborow - I probably won't look at this today. If you want to play with it, feel free. I'd start with reverting the change from that commit in April, then removing Gemfile.lock and seeing if both the built gem and a bundle --deployment version work. If you don't get to it, no worries. I'll try to take a look tomorrow.

[tobias]

@davidglassborow - are you using the master branch (for TorqueBox 1.x) or the torquebox-2x branch?

[davidglassborow]

@tobias - At the time I was using the 2x branch

[tobias]

I figured it out - BackStage runs under ruby 1.9 mode, so the gems have to be installed under 1.9. To do that, try:

jruby --1.9 -S bundle install --deployment

If you run into any problems, feel free to reopen this issue.