[erlang-questions] Rebar dependency tracking

Dmitry Kolesnikov <>
Wed Nov 18 20:29:17 CET 2015


There should be a flat structure of deps unless you mess-up with rebar.config
Do you have any {deps_dir, …}. directive in rebar.config of B,C, or A projects?

- Dmitry

> On Nov 18, 2015, at 8:58 PM, Constantine Povietkin <> wrote:
> 
> В Wed, 18 Nov 2015 20:34:47 +0200
> Dmitry Kolesnikov <> пишет:
> 
> No, B depends on the version as B does. 
> 
> Message: could find file or directory.
> 
> And "deps" folder for B is empty.
> 
>> Hi,
>> 
>> It should work. I might assume that B depends on diff version of C 
>> Can you share error message with us?
>> 
>> Best Regards, Dmitry
>> 
>> 
>>> On Nov 18, 2015, at 7:22 PM, Constantine Povietkin
>>> <> wrote:
>>> 
>>> Hi all! 
>>> 
>>> I have an application that depends on other applications with its
>>> own dependencies.
>>> 
>>> 		A
>>> 	/		\
>>> 	B		C
>>> 	/\
>>> 	C D
>>> 
>>> Rebar get-deps command fetches dependencies to the A deps folder.
>>> As a result dependency B could not be compiled because of missing
>>> dependency.
>>> 
>>> I use rebar 2.5.0.
>>> 
>>> rebar.config:
>>> 
>>> {deps, [
>>>   {C, ".*", {git, "git_path_to_dependecy", {tag, "v1.0.0"}}},
>>>   {B, ".*", {git, "git_path_to_dependecy", {tag, "v1.0.0"}}},
>>> ]}.
>>> 
>>> 
>>> What am I doing wrong? Or where can I read about dependency tracking
>>> more detail?
>>> 
>>> Thanks in advance.
>>> _______________________________________________
>>> erlang-questions mailing list
>>> 
>>> http://erlang.org/mailman/listinfo/erlang-questions
>> 
> 



More information about the erlang-questions mailing list