Skip to content
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

Running a warbler generated war: Could not find jruby-openssl-0.9.21-java in any of the sources #486

Open
akcrono opened this issue Nov 19, 2020 · 4 comments

Comments

@akcrono
Copy link

akcrono commented Nov 19, 2020

Bundling and generating war files via bundle exec warble runnable war run fine, but when trying to run a war file generated by warbler via java -jar cdc.war -S rake -T results in the this error:

Bundler::GemNotFound: Could not find jruby-openssl-0.9.21-java in any of the sources
  materialize at /tmp/jruby2323949162897933825extract/gems/gems/bundler-1.17.3/lib/bundler/spec_set.rb:91
         map! at org/jruby/RubyArray.java:2609
  materialize at /tmp/jruby2323949162897933825extract/gems/gems/bundler-1.17.3/lib/bundler/spec_set.rb:85
        specs at /tmp/jruby2323949162897933825extract/gems/gems/bundler-1.17.3/lib/bundler/definition.rb:170
    specs_for at /tmp/jruby2323949162897933825extract/gems/gems/bundler-1.17.3/lib/bundler/definition.rb:237
        setup at /tmp/jruby2323949162897933825extract/gems/gems/bundler-1.17.3/lib/bundler/runtime.rb:20
        setup at /tmp/jruby2323949162897933825extract/gems/gems/bundler-1.17.3/lib/bundler.rb:109

jruby: 9.1.17.0, bundler 1.17.3, warbler 2.0.5

It appears that this is an issue related to bundling default gems and has been present for others (#482 , #472, #376), but there has been no solution that I can find. I attempted to run with bundler 2.1.4, and received the same error for rake-10.5.0 instead.

@akcrono
Copy link
Author

akcrono commented Nov 20, 2020

Walking through how warbler handles dependencies, it looks like full_gem_path.exist? is false, caused by a missing gems directory for jruby-openssl in shared/gems. The spec file still exists as part of the shared/specifications/default directory.

warn "skipping #{spec.name} default gem (assuming its part of jruby-jars #{JRubyJars::VERSION})" is suppressed, making this failure silent.

The jruby dist is from maven, found here

@headius
Copy link
Member

headius commented Jan 15, 2021

Sorry this has has no responses! Could you provide a simple example we can use to reproduce the issue?

@akcrono
Copy link
Author

akcrono commented Feb 23, 2021

Sorry for the delay. Apparently the issue was caused by the jruby-jars gem version not matching the jruby version. Might be worthwhile to make the warning for the mismatch more explicit and not suppressed.

@headius
Copy link
Member

headius commented Feb 23, 2021

@akcrono That is a good idea. Thanks for following up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants