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/20 00:40:12 UTC

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

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

Peter Donald closed BUILDR-705.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.21
         Assignee: Peter Donald

I have merged this into master and it will be released next version. 

Thanks!

> 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
>            Assignee: Peter Donald
>             Fix For: 1.4.21
>
>         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)