Charles Oliver Nutter

@kares @mkristian @enebo @jkutner Is this something we want to pursue?

So basically we would switch the current logic from using JBundler to copy in the jars and instead use Jars::Lock?

I have seen this message for other gems that would have a C extension on CRuby, but skip building the extension on JRuby (falling back on a pure-Ruby or Java-based...

So it's only this library you seem to have trouble with? I know that `http-parser` has a native component that has to be build and shipped... so that would definitely...

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...

Nevermind previous comment if it came through, I did not notice you *did* file it with Warbler. Yes, this would be a good fix!

A repro would be helpful, sure! Not sure when I will circle back to this but any assistance you provide will help others contribute.

@fzakaria Thank you!

I assume this isn't resolved by my fix for jruby/jruby#6045 but I have not yet looked into it.

Good point. I don't think the intent was to prevent commercial use, but I am not sure of the lineage of the related word list.