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 2015/02/07 09:52:34 UTC

[jira] [Commented] (BUILDR-705) Remove runtime dependency on rspec

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

Peter Donald commented on BUILDR-705:
-------------------------------------

Hi, I will try to have a look at doing this sometime next weekend. Unfortunately what we are going to have to do to keep a nice user experience is to detect when a build uses the check method and Rspec is not present to give a warning to user to add the rspec dependency. I think this can probably be done using method_missing and will give it a try next weekend.

> Remove runtime dependency on rspec
> ----------------------------------
>
>                 Key: BUILDR-705
>                 URL: https://issues.apache.org/jira/browse/BUILDR-705
>             Project: Buildr
>          Issue Type: Bug
>          Components: Dependency management
>    Affects Versions: 1.4.20
>         Environment: OS X 10.10
>            Reporter: r6p
>         Attachments: 0001-Removing-runtime-dependency-on-rspec.patch
>
>
> Having rspec as a "runtime dependency" for buildr is blocking us from updating rspec. Since using buildr's rspec support is optional and we don't use it, but use rspec directly ourselves this prevents us from upgrading rspec in our codebase due to version conflicts since we include buildr in our Gemfile.
> I think it makes sense to ask users to include rspec separately in their Gemfile and control the correct version required to make use of buildr's rspec support if that want to use that feature of buildr. But this shouldn't block those of us who don't use buildr from upgrading our independent rspec dependencies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)