warbler Allow packaging using MRI

Hi!

It looks like we need to use JRuby command line to package with Warbler even if the actual JRuby to be packaged comes from the jruby-jars gem. It would be nice to be able to use MRI for packaging since then I would not have to care about it. MRI, JRuby, Rubinius, whatever. No problem.

Also, MRI is a faster on the command line due to faster startup.

Currently, I get the C version of gems when packaging with MRI, for example the thread_safe gem.

Any chance we can run the gem bundling so that the Java versions of the gems are used?

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/15885999-allow-packaging-using-mri?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github).

May 19 '15 08:05 donv

Oh yea, that's definitely something we want to support. We actually run tests on CI against MRI (and ironically they are the ones passing right now).

But i didn't realize MRI was pulling in the wrong gems. I'm not sure how to fix that, but i do want to fix it.

May 19 '15 13:05 jkutner

quite unfortunate but inevitable with platform specific gems, it's a bit of a hack since how do we force you to have the -java (JRuby) version of the gem installed under MRI ... while it should be possible to pull those there would be a general assumption that those gems install fine (smt gem authors certainly do not test for).

Jun 28 '15 16:06 kares

We do that hack in Ruboto, and it does work.

A better solution is to implement a "--platform" option to "bundle install".

Jun 28 '15 18:06 donv

Any progress on this front?

Jul 28 '20 13:07 HarlemSquirrel