-
Notifications
You must be signed in to change notification settings - Fork 201
-
Notifications
You must be signed in to change notification settings - Fork 201
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
private method `require' called for Bundler:Module #62
Comments
I suspect this is related to this: |
This is only on latest, 1.3.2 works fine (I'm using latest because I'm running 1.6.5) In Tomcat, the following...
Comes out as Looks like the change was made here: 404b9ba |
Yeah, probably because Maybe you can investigate why |
Would this be portable enough? https://github.com/lstoldt/warbler/commit/5bab3df1584f3ca76e76cc1623057ea70abf8545 Its using something similiar already for setting Glassfish, Resin, and Tomcat expand the war, and I have this problem on at least Glassfish and Tomcat. |
I'm getting this issue as well on jruby 1.6.5 deployed to tomcat using warbler 1.3.3 running in 1.8 mode. Here is the full error: https://gist.github.com/1423442 This error started happening for me when upgrading from warbler 1.3.2 to 1.3.3. |
@lstoldt can you see what happens if you set Also, your patch is unfortunately too specific to the web environment -- Warbler can create executable jars that use Bundler and thus would not have access to |
@atambo: so you see the issue just by upgrading to 1.3.3? |
@nicksieger, yes, my only change was upgrading warbler from 1.3.2 to 1.3.3 and that causes this error when deploying on tomcat. |
Adding that line to my warble config gave me the same error using 1.3.3. I'll look into this some more and make sure its getting to that method in JRuby-Rack and see what it coming up with. |
Same error for me when I deploy a war file on Tomcat 6.0.24, JRuby 1.6.5, Rails 3.1.3 and Warbler 1.3.3. With Warbler 1.3.2 it's OK. |
Reproduced on Tomcat 7.0.23, jruby-1_6 head, Rails 3.1 & warbler 1.3.3; reverting to warbler 1.3.2 resolves issue. |
Sorry gang. Looks like 1.3.3 might be a bad release. Considering yanking it on rubygems.org to give me some more time to sort out the issue. Thoughts? |
Any updates on this issue? |
Note: Here's my workaround for 1.3.2, until Nick gets this sorted. |
fixed along with #62 |
1.3.4 is out with the fix for this issue! Please try it with your applications and report back. Thanks for your patience! |
This fix worked for me, I can now deploy against tomcat 7 with warbler version 1.3.4. |
Great, thanks for the quick feedback @atambo! |
Same for me ! Thanks @nicksieger. |
Thanks @nicksieger you saved my day |
I confirmed the Bundler gem is included in the war.
Trying to run 1.9 (this is after changing "require" to "require_relative" in yaml.rb)
The text was updated successfully, but these errors were encountered: