You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2011/06/22 12:11:18 UTC

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

     [ https://issues.apache.org/jira/browse/BUILDR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Donald closed BUILDR-256.
-------------------------------


> 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
>            Assignee: Antoine Toulme
>            Priority: Minor
>             Fix For: 1.4.2
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira