-
Notifications
You must be signed in to change notification settings - Fork 40
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
Latest jbundler fails to run jbundle
#58
Comments
oh - it looks like a regression in ruby-maven-3.1.1.0.10 since the stacktrace indicates in can not find jruby. try to use your build for next release of ruby-maven (will be soon) ;) |
the problem was that version of the bundled telsa-polyglot-ruby needs to be on maven-central to load on the fly the missing jruby bits. this is build of 0.1.2-SNAPSHOT with get relabled with 0.1.1 (bad thing but repo needs a new home once maven-3.6.2 is released and then rectify this version mess) fixes mkristian/jbundler#58 Sponsored by Lookout Inc.
just pushed ruby-maven-3.1.1.0.11.gem and it fixes my project which saw the same problem: https://travis-ci.org/lookout/leafy/builds/51107729 |
Sorry I never responded here, @mkristian. The release of ruby-maven-3.1.1.0.11 fixed the issue for me in February, but has unfortunately resurfaced. I'm getting the same error using jruby 1.7.20.1, jbundler 0.7.4, bundler 1.10.3, and rubygems 2.4.8 running inside a docker container. I tried putting jruby.jar on the classpath, but that didn't seem to work :( Any ideas? |
sorry for the late replay as well. I release jbundler-0.8.0 which should fix your problem. jruby-1.7.20.1 comes with ruby-maven 3.1.1.0.8 - not sure if this is the problem. try to get new version in for jruby-1.7.21 |
The latest jbundler and dependencies don't seem to be working, and I have no idea why. jbundler is part of my gemfile, so I run
bundle
, thenbundle exec jbundle
. I get an error that saysjava.lang.NoClassDefFoundError: org/jruby/embed/ScriptingContainer
. Please see this travis build for a full stack trace.I managed to solve the problem by locking jbundler and dependencies to specific versions. Here's what my gemfile looks like now:
Any idea why this might be happening with the latest jbundler and dependencies?
The text was updated successfully, but these errors were encountered: