From: KOSAKI Motohiro Date: 2012-07-03T11:58:59+09:00 Subject: [ruby-core:46125] Re: [ruby-trunk - Feature #6590] Dealing with bigdecimal, etc gems in JRuby On Mon, Jul 2, 2012 at 10:51 AM, Aaron Patterson wrote: > On Sun, Jul 01, 2012 at 04:22:59PM +0900, mrkn (Kenta Murata) wrote: >> >> Issue #6590 has been updated by mrkn (Kenta Murata). >> >> >> I don't know how do I allow the JRuby team to uload the Java version of BigDecimal. >> What should I do? > > You can add headius like this: > > $ gem owner -a headius@example.org bigdecimal > > But you need his rubygems.org email address. > > Charlie, would this be a sufficient solution for now? I suspect that > all stdlib gems suffer from this same problem. We should think about a > better solution. Whenever a CRuby stdlib gem with native code is released, > an equivalent JRuby gem should be released too. How can we accomplish > that? I dislike this idea at all. If we take it, bigdecimal gem evetually has c, java, C#, haskel, pascal, etc implementations when we get more and more various ruby interpreter. Actually, this is not bigdecimal issue. It is gem discovery issue. MRI support two extension types, C and Ruby. JRuby also support two extension types, Java and Ruby. gem loader should realized the fact and prefer to look up Java implementation when used from JRuby. I think.