Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: JRuby 1.6RC2
-
Fix Version/s: JRuby 1.6RC3
-
Component/s: Core Classes/Modules
-
Labels:None
-
Number of attachments :
Description
When launching a child "ruby" or "jruby" instance in the same JVM, we are still looking at System.getenv for RUBYOPT, even though we pass a new pseudo-environment along to the pseudo-child. This causes RubyGems update to fail on older versions of JRuby since a RUBYOPT=rubygems env var will cause both versions of RubyGems to get loaded.
This causes JRUBY-5509, which is also tracked in the following RubyGems issue:
http://rubyforge.org/tracker/index.php?func=detail&aid=28924&group_id=126&atid=575
Fix pending.
Activity
Charles Oliver Nutter
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Charles Oliver Nutter
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
commit 780ba75ce627bfafc7d93f27f57dc518345c5361
Author: Charles Oliver Nutter <headius@headius.com>
Date: Wed Feb 16 16:00:01 2011 -0600
Fix
JRUBY-5517: RUBYOPT is pulled from system env always, even for in-process child