RUBYOPT is pulled from system env always, even for in-process child
-------------------------------------------------------------------
Key: JRUBY-5517
URL: http://jira.codehaus.org/browse/JRUBY-5517
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.6RC2
Reporter: Charles Oliver Nutter
Assignee: Charles Oliver Nutter
Fix For: JRuby 1.6RC3
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email