Charles Oliver Nutter

There's now multiple stdlib gems that fake out extensions on JRuby, and they show warnings when run in verbose mode. I'm about ready to monkey-patch `missing_extensions?` to no-op on JRuby...

Revisiting this once again. I guess RubyGems must be using our value for `RbConfig::CONFIG['arch']` because that matches the platform location it's using: `universal-java21`. The problem is that C libraries built...

Some background... We originally added the Java version to our `arch` waaaaaay back in 2007: https://github.com/jruby/jruby/commit/03d436908e3637814ddd283f1b8ca8ae7de43624 At the time we were just trying to match the level of detail that...

@deivid-rodriguez I'm also willing to try removing the Java version from our `arch` field, since it's not really being used by anyone to enforce a specific ABI (other than an...

Before I forget: there is still some debate in my mind about using this `arch` to determine a platform at all. Native libraries built under JRuby obviously do still have...

I've pushed jruby/jruby#8883 which normalizes the arch platform and version to be similar to CRuby. This should allow the Bundler fix to work now and any future RubyGems fix to...

The PR in jruby/jruby#8883 looks fine in CI, but I just realized that RG or Bundler must already be normalizing the version? This output is from a version of JRuby...

I had a chat with @p0deje at RubyKaigi and wanted to summarize how this stuff works in JRuby. Our recommendation for most gems that have jar dependencies is to use...

Sorry I missed this for a while. Answers to some questions: ## I don't think this is the right fix because it will hide all instances of this warning in...

The jruby-launcher gem actually exposes another problem with this warning: it does not actually create an extension for the `missing_extension?` check to find. Instead, it just builds an executable that...