Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: JRuby 1.6.6
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Solaris
    • Number of attachments :
      0

      Description

      Since updating from 1.6.5.1 to 1.6.6/7, gem support has been broken with JRuby. Excuting jgem list shows no installed gems, as soon as I swap out jruby.jar for 1.6.5.1, everything works just fine.

        Activity

        Hide
        Hiro Asari added a comment -

        What does jruby -S gem env show (for both 1.6.7 and 1.6.5.1)? Do you have anything set in JRUBY_OPTS?

        Show
        Hiro Asari added a comment - What does jruby -S gem env show (for both 1.6.7 and 1.6.5.1)? Do you have anything set in JRUBY_OPTS ?
        Hide
        victor igumnov added a comment -

        1.6.5.1:

        RubyGems Environment:

        • RUBYGEMS VERSION: 1.5.1
        • RUBY VERSION: 1.8.7 (2011-12-27 patchlevel 330) [java]
        • INSTALLATION DIRECTORY: /opt/jruby/lib/ruby/gems/1.8
        • RUBY EXECUTABLE: /opt/jruby/bin/jruby
        • EXECUTABLE DIRECTORY: /opt/jruby/bin
        • RUBYGEMS PLATFORMS:
        • ruby
        • universal-java-1.6
        • GEM PATHS:
        • /opt/jruby/lib/ruby/gems/1.8
        • /root/.gem/jruby/1.8
        • GEM CONFIGURATION:
        • :update_sources => true
        • :verbose => true
        • :benchmark => false
        • :backtrace => false
        • :bulk_threshold => 1000
        • "install" => "--no-rdoc --no-ri"
        • "update" => "--no-rdoc --no-ri"
        • REMOTE SOURCES:
        • http://rubygems.org/

        1.6.7:

        RubyGems Environment:

        • RUBYGEMS VERSION: 1.5.1
        • RUBY VERSION: 1.8.7 (2012-02-22 patchlevel 357) [java]
        • INSTALLATION DIRECTORY: /opt/jruby/lib/ruby/gems/1.8
        • RUBY EXECUTABLE: /opt/jruby/bin/jruby
        • EXECUTABLE DIRECTORY: /opt/jruby/bin
        • RUBYGEMS PLATFORMS:
        • ruby
        • universal-java-1.6
        • GEM PATHS:
        • /opt/jruby/lib/ruby/gems/1.8
        • /root/.gem/jruby/1.8
        • GEM CONFIGURATION:
        • :update_sources => true
        • :verbose => true
        • :benchmark => false
        • :backtrace => false
        • :bulk_threshold => 1000
        • "install" => "--no-rdoc --no-ri"
        • "update" => "--no-rdoc --no-ri"
        • REMOTE SOURCES:
        • http://rubygems.org/

        And no JRUBY_OPTS defined.

        Show
        victor igumnov added a comment - 1.6.5.1: RubyGems Environment: RUBYGEMS VERSION: 1.5.1 RUBY VERSION: 1.8.7 (2011-12-27 patchlevel 330) [java] INSTALLATION DIRECTORY: /opt/jruby/lib/ruby/gems/1.8 RUBY EXECUTABLE: /opt/jruby/bin/jruby EXECUTABLE DIRECTORY: /opt/jruby/bin RUBYGEMS PLATFORMS: ruby universal-java-1.6 GEM PATHS: /opt/jruby/lib/ruby/gems/1.8 /root/.gem/jruby/1.8 GEM CONFIGURATION: :update_sources => true :verbose => true :benchmark => false :backtrace => false :bulk_threshold => 1000 "install" => "--no-rdoc --no-ri" "update" => "--no-rdoc --no-ri" REMOTE SOURCES: http://rubygems.org/ 1.6.7: RubyGems Environment: RUBYGEMS VERSION: 1.5.1 RUBY VERSION: 1.8.7 (2012-02-22 patchlevel 357) [java] INSTALLATION DIRECTORY: /opt/jruby/lib/ruby/gems/1.8 RUBY EXECUTABLE: /opt/jruby/bin/jruby EXECUTABLE DIRECTORY: /opt/jruby/bin RUBYGEMS PLATFORMS: ruby universal-java-1.6 GEM PATHS: /opt/jruby/lib/ruby/gems/1.8 /root/.gem/jruby/1.8 GEM CONFIGURATION: :update_sources => true :verbose => true :benchmark => false :backtrace => false :bulk_threshold => 1000 "install" => "--no-rdoc --no-ri" "update" => "--no-rdoc --no-ri" REMOTE SOURCES: http://rubygems.org/ And no JRUBY_OPTS defined.
        Hide
        Hiro Asari added a comment -

        Why do you have RubyGems 1.5.1 on JRuby 1.6.7? We shipped with 1.8.15. https://github.com/jruby/jruby/commit/333c503

        $ git name-rev 333c503
        333c503 tags/1.6.6.RC1
        

        Even JRuby 1.6.5.1 shipped with RubyGems 1.8.9. (https://github.com/jruby/jruby/commit/fe66715)

        Does jruby -S gem list behave any differently?

        Show
        Hiro Asari added a comment - Why do you have RubyGems 1.5.1 on JRuby 1.6.7? We shipped with 1.8.15. https://github.com/jruby/jruby/commit/333c503 $ git name-rev 333c503 333c503 tags/1.6.6.RC1 Even JRuby 1.6.5.1 shipped with RubyGems 1.8.9. ( https://github.com/jruby/jruby/commit/fe66715 ) Does jruby -S gem list behave any differently?
        Hide
        victor igumnov added a comment -

        You are absolutely right, as soon as I updated RubyGems, 1.6.7 finds the locally installed gems.

        Show
        victor igumnov added a comment - You are absolutely right, as soon as I updated RubyGems, 1.6.7 finds the locally installed gems.

          People

          • Assignee:
            Thomas E Enebo
            Reporter:
            victor igumnov
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: