[
https://issues.apache.org/jira/browse/BUILDR-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14321321#comment-14321321
]
Peter Donald commented on BUILDR-705:
-------------------------------------
I managed to allocate some time to this and have created a branch that tries to
fix the whole issue. In particular it ensures that a warning message is issued
if rspec features are used but the dependency is not activated and it ensues
that the tests will continue to work.
The branch exists at: https://github.com/apache/buildr/compare/BUILDR-705
> 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)
