[jira] Commented: (BUILDR-256) Automatically installing gems aborts rspec test runner

["Rhett Sutphin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BUILDR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778673#action_12778673 ] 

Rhett Sutphin commented on BUILDR-256:
--------------------------------------

The same monkey patch will work with buildr 1.3.5 and jruby 1.3.1 (rubygems 1.3.3) with the following changes:

- Replace "Kernel.gem name, version" with "Kernel.send :gem, name, version"
- Remove the Gem.manage_gems line

> Automatically installing gems aborts rspec test runner
> ------------------------------------------------------
>
>                 Key: BUILDR-256
>                 URL: https://issues.apache.org/jira/browse/BUILDR-256
>             Project: Buildr
>          Issue Type: Bug
>    Affects Versions: 1.3.3
>         Environment: RubyGems 1.2.0
>            Reporter: Rhett Sutphin
>            Priority: Minor
>             Fix For: 1.4
>
>
> The automatic jruby gem installer code (the template for which is created by the jruby_gem method in TestFramework::JRubyBased) uses Gem::GemRunner to automatically install gems.  GemRunner (at least in RubyGems 1.2.0) always throws Gem::SystemExitException when it completes.  This aborts the runner and returns control to buildr.  Buildr then fails with an exception because result.yaml doesn't exist.
> Workaround: each run will successfully install one of the gems, so you can run the test several times to install all the gems.  Alternatively, you can manually install the necessary gems using jruby -S gem install.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.