[
https://issues.apache.org/jira/browse/BUILDR-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266639#comment-13266639
]
Russell Teabeault commented on BUILDR-636:
------------------------------------------
For example, we have some tasks that use net-ssh. There was a bug in net-ssh
that caused thread deadlocks but had been fixed in newer versions than that
specified by buildr. However, we couldn't use this newer version because
buildr had the version locked. To get around this problem we had to upgrade
buildr's version and then create and host our own version of the buildr gem.
I would vote for a more laxed policy on gem dependencies except for those which
cause known problems. Another potential solution would be more frequent buildr
releases. I will bring that topic up in the dev mailing list.
> Do not set hard version numbers for gem dependencies unless absolutely
> necessary
> --------------------------------------------------------------------------------
>
> Key: BUILDR-636
> URL: https://issues.apache.org/jira/browse/BUILDR-636
> Project: Buildr
> Issue Type: Dependency upgrade
> Affects Versions: 1.4.6, 1.4.7
> Reporter: Russell Teabeault
>
> I am finding more and more that buildr's gem dependencies are causing
> conflicts with my own project's gem requirements. This is typically because
> the version in the gemspec is set to a specific version instead of a minimum
> version.
> For example in buildr.gemspec,
> spec.add_dependency 'rake', '0.8.7'
> probably should be
> spec.add_dependency 'rake', '>= 0.8.7'
> unless there is a good reason that it only works with rake 0.8.7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
