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

Russell Teabeault updated BUILDR-636:
-------------------------------------

    Description: 
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.

  was:
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.

    
> 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

        

Reply via email to