[ 
https://issues.apache.org/jira/browse/BUILDR-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045967#comment-15045967
 ] 

Antoine Toulme edited comment on BUILDR-710 at 2/14/17 7:15 AM:
----------------------------------------------------------------

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

{code}
ruby 
gem 'buildr', '= 1.4.23'
{code}

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


was (Author: pdonald):
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

```ruby 
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: https://issues.apache.org/jira/browse/BUILDR-710
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.4.21
>            Reporter: Thibault Kruse
>            Assignee: Peter Donald
>            Priority: Minor
>             Fix For: 1.5.1
>
>
> 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 "https://rubygems.org";
> 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: 
> http://www.forumjar.com/forums/topic/Apache_Buildr_gets_confused_over_Gemfile#sthash.Rivie2GQ.dpuf



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to