JRuby

Consider RubyGems 1.4.1 for JRuby 1.6.0

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: JRuby 1.6RC1
  • Fix Version/s: JRuby 1.6RC1
  • Component/s: Miscellaneous
  • Labels:
    None
  • Number of attachments :
    0

Description

RubyGems 1.4.1 has been released. http://blog.zenspider.com/2010/12/rubygems-version-140-has-been.html mentions that MRI 1.9.2 has problems, but does not mention JRuby.

My limited testing shows that JRuby can serve a Rails 3.0.3 app with glassfish gem 1.0.3 using RubyGems 1.4.1.

This is not to say that we are clean, since we do have customization done in gem_prelude.rb.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. JRUBY-5217 RubyGems Maven doesn't like alphanumeric versions

  • Major - Major loss of function.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Hiro Asari added a comment -

If you try to update RubyGems to 1.4.1 on MRI 1.9.2, we get:

[❼-1.8.7-p330]:~ $ rvm use 1.9.2
Using /Users/asari/.rvm/gems/ruby-1.9.2-p136
[❷-1.9.2-p136]:~ $ ruby -S gem update --system
Updating RubyGems
Updating rubygems-update
Successfully installed rubygems-update-1.4.1
Updating RubyGems to 1.4.1
Installing RubyGems 1.4.1
/Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/source_index.rb:62:in `installed_spec_directories': undefined method `path' for Gem:Module (NoMethodError)
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/source_index.rb:52:in `from_installed_gems'
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:914:in `source_index'
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/gem_path_searcher.rb:98:in `init_gemspecs'
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/gem_path_searcher.rb:13:in `initialize'
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:873:in `new'
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:873:in `searcher'
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:495:in `find_files'
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:1034:in `load_plugins'
	from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/gem_runner.rb:84:in `<top (required)>'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from <internal:lib/rubygems/custom_require>:29:in `require'
	from setup.rb:25:in `<main>'

This does not happen with the master branch, so that's another encouraging sign.

Show
Hiro Asari added a comment - If you try to update RubyGems to 1.4.1 on MRI 1.9.2, we get: [&#10108;-1.8.7-p330]:~ $ rvm use 1.9.2 Using /Users/asari/.rvm/gems/ruby-1.9.2-p136 [&#10103;-1.9.2-p136]:~ $ ruby -S gem update --system Updating RubyGems Updating rubygems-update Successfully installed rubygems-update-1.4.1 Updating RubyGems to 1.4.1 Installing RubyGems 1.4.1 /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/source_index.rb:62:in `installed_spec_directories': undefined method `path' for Gem:Module (NoMethodError) from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/source_index.rb:52:in `from_installed_gems' from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:914:in `source_index' from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/gem_path_searcher.rb:98:in `init_gemspecs' from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/gem_path_searcher.rb:13:in `initialize' from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:873:in `new' from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:873:in `searcher' from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:495:in `find_files' from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems.rb:1034:in `load_plugins' from /Users/asari/.rvm/gems/ruby-1.9.2-p136/gems/rubygems-update-1.4.1/lib/rubygems/gem_runner.rb:84:in `<top (required)>' from <internal:lib/rubygems/custom_require>:29:in `require' from <internal:lib/rubygems/custom_require>:29:in `require' from setup.rb:25:in `<main>' This does not happen with the master branch, so that's another encouraging sign.
Hide
Permalink
Hiro Asari added a comment -

RubyGems 1.4.1 breaks maven integration, as noted in JRUBY-5217.

Show
Hiro Asari added a comment - RubyGems 1.4.1 breaks maven integration, as noted in JRUBY-5217 .
Hide
Permalink
Hiro Asari added a comment -

Hmm. After 2b08a57 (rather than jruby -S gem update --system), the maven gem seems to work fine.

Since Charlie updated RubyGems with the above commit, I'm going to resolve this.

Show
Hiro Asari added a comment - Hmm. After 2b08a57 (rather than jruby -S gem update --system ), the maven gem seems to work fine. Since Charlie updated RubyGems with the above commit, I'm going to resolve this.

People

  • Assignee:
    Charles Oliver Nutter
    Reporter:
    Hiro Asari
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: