buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Donald (JIRA)" <>
Subject [jira] [Commented] (BUILDR-710) Buildr gets confused over Gemfile
Date Mon, 07 Dec 2015 23:14:11 GMT


Peter Donald commented on BUILDR-710:

Buildr does this by design. Bundler/Gemfiles are the standard ruby mechanism for managing
dependencies. And Buildr assumes that if you have a Gemfile present that you want to manage
the dependencies of Buildr via the Gemfile. So to get this working you should add the line

gem 'buildr', '= 1.4.23'

To your Gemfile to get buildr declared as a dependency and then `bundle install` to load the
dependencies and then you should be able to run the build as per usual

> Buildr gets confused over Gemfile
> ---------------------------------
>                 Key: BUILDR-710
>                 URL:
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.4.21
>            Reporter: Thibault Kruse
>            Priority: Minor
> Hi,
> Using buildr-1.4.23
> I had a Gemfile in my current Dir hwen invoking buildr, leading to buildr failing with
errors like:
> Could not find addressable-2.3.8 in any of the sources
> Run `bundle install` to install missing gems.
> The Gemfile was:
> {code}
> source ""
> gem "jekyll"
> gem "html-proofer"
> gem "asciidoctor-pdf"
> gem "coderay"
> gem "pygments.rb"
> {code}
> I don't know if that is standard ruby behavior maybe, but I feel buildr should not care
whether a gemfile is present or not. - See more at:

This message was sent by Atlassian JIRA

View raw message