New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jruby-openssl doesn't get packaged in war file #339
Comments
@atambo which jruby version are you using for packing the war ? which warbler or jruby-jars version ? it sounds like a default gem problem. |
It is jruby-jars 1.7.22 and warbler 1.4.9. |
So I set my Gemfile to use jruby-openssl 0.9.11 (while the packaged one in jruby-jars is 0.9.10) and now the gem is within the war file and bundler can find it. So I'd say this is a bug where bundler within a war file cannot find the default gems. |
yes, but a difficult one. bundler does not include default gems in its Gemfile.lock. the Gemfile.lock does depend on the jruby version with which it got created. the jruby (or MRI) you are using to run warbler does not know about the default gems used creating the Gemfile.lock or for the jruby which goes into the war file. hope you get the idea what I try to say - there is not "descriptor" for those embedded default gems. |
this is a generic issue with default gems ... we'll need to adjust/patch |
When putting 'jruby-openssl' into my Gemfile and then deploying the war I get:
I also get the error if I put
config.gems += ["jruby-openssl"]
into my warble.rb configuration.The text was updated successfully, but these errors were encountered: