On second thought, it's probably a gems/RubyForge problem. JRuby gems used to be named -jruby.gem so we had continued this naming scheme. But gems 1.0 changed the way the architecture/platform distinction is handled, and now builds gems that end in -java.gem. RubyForge probably updated to the gems 1.0 indexer and stopped indexing -jruby gems.
I dunno whether JRuby can install -jruby, or -java, or both. I uploaded a gem ending in -java so we will see. Evan On Dec 23, 2007 12:23 AM, Evan Weaver <[EMAIL PROTECTED]> wrote: > The remaining issue is why JRuby didn't find that build in the gem > index and installed 1.0.2 instead. Seems like a JRuby problem to me? > > Evan > > On Dec 22, 2007 11:57 PM, Stephen Bannasch > <[EMAIL PROTECTED]> wrote: > > > I was able to get the mongrel gem installed in JRuby by first > > compiling it with MRI but specifying java: > > > > $ svn co http://mongrel.rubyforge.org/svn/trunk mongrel > > $ cd mongrel > > $ rake package java > > > > then in JRuby > > > > $ cd mongrel/pkg > > $ gem install mongrel-1.1.2-java.gem > > Successfully installed mongrel-1.1.2 > > 1 gem installed > > Installing ri documentation for mongrel-1.1.2... > > Installing RDoc documentation for mongrel-1.1.2... > > > > > > _______________________________________________ > > Mongrel-users mailing list > > Mongrel-users@rubyforge.org > > http://rubyforge.org/mailman/listinfo/mongrel-users > > > > > > -- > Evan Weaver > Cloudburst, LLC > -- Evan Weaver Cloudburst, LLC _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
