-
Notifications
You must be signed in to change notification settings - Fork 205
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
WAR files give error "Could not find http-parser-1.2.1 in any of the sources" #482
Comments
So it's only this library you seem to have trouble with? I know that |
For what it's worth, it does look like the native C code made it into the WAR. Here is what I get from running
|
This has also been reported in a different form in #472, where the sassc library needs to be able to build and load a native library that it binds with FFI. |
I have similar problem with sassc. I debugged it to the point that sassc spec is skipped because it is missing extensions. gem.build_complete file is not included in application.war. I am using warbler 2.0.5, jruby 9.2.11.0 with rvm. Bundler version 1.17.3 sassc gems installed into rvm gems has gem.build_complete files and everthing works when running rails with puma. Making application.war does not work inside tomcat and error is Bundler::GemNotFound: Could not find sassc-2.0.1 in any of the sources this problem does not exist with bundler 2.1.4 |
Warbler appears to not be playing nicely with the http-parser gem. I followed the following steps on jruby 9.2.11.1 to create a WAR file of a basic rails app with http-parser in the Gemfile:
I also tried
warble compiled war
. Both times, when I put the WAR file into tomcat, I got the following error in my browser:Could not find http-parser-1.2.1 in any of the sources
I can run
rails s
no problem, and get no problems when I use http-parser in my app locally. It's only when I try to run the WAR file that I get problems.I am using bundler 2.1.4. I tried this on both Windows and Linux.
The text was updated successfully, but these errors were encountered: