This is actually fixed in the jruby-1_6 branch. It will be included in the 1.6.3 release.
-----Original Message----- From: Patrik Sundberg (JIRA) [mailto:j...@codehaus.org] Sent: Thursday, July 07, 2011 4:12 AM To: dev@jruby.codehaus.org Subject: [jruby-dev] [jira] Created: (JRUBY-5908) exec regression in windows since 1.6.0 (?) exec regression in windows since 1.6.0 (?) ------------------------------------------ Key: JRUBY-5908 URL: https://jira.codehaus.org/browse/JRUBY-5908 Project: JRuby Issue Type: Bug Affects Versions: JRuby 1.6.2 Environment: jruby 1.6.2 (ruby-1.8.7-p330) (2011-05-23 e2ea975) (Java HotSpot(TM) Client VM 1.6.0_21) [Windows XP-x86-java] Reporter: Patrik Sundberg Assignee: Thomas E Enebo Running into the following when using the gem gemedit to easily open installed gems in an editor. What it does is essentially this: {code:title=edit_command.rb} cmd = "#{options[:editor]} ." Dir.chdir(spec.full_gem_path) do exec cmd end {code} This used to work ok on 1.6.0 under windows. However, now it doesnt seem like exec searches the PATH anymore when firing up the editor. I get: ERROR: While executing gem ... (Errno::ENOENT) No such file or directory - cannot execute If I set the full path to the editor I get the odd effect of the editor opening, but in the current directory where I issue the command, not spec.full_gem_path. I assume something must have changed with regards to #exec on windows between 1.6.0 and 1.6.2. -- This message is automatically generated by JIRA. 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 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
