<html><head></head><body>Applications in erlang represent a flat list, so there may be only one version of an application used in runtime. Rebar expects all your dependencies to reside in the ≤top-directory≥/deps after rebar get-deps. The dependencies would use this exact folder to look for their own dependencies, so there would be no ./deps/*/deps directories. <br>
<br>
<br>
-- <br>
Best wishes,<br>
Dmitry Belyaev<br><br><div class="gmail_quote">On 19 November 2015 4:22:14 AM AEDT, Constantine Povietkin <povetkin.k@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi all! <br /><br />I have an application that depends on other applications with its own<br />dependencies.<br /><br /> A<br /> / \<br /> B C<br /> /\<br /> C D<br /><br />Rebar get-deps command fetches dependencies to the A deps folder. As a<br />result dependency B could not be compiled because of missing dependency.<br /><br />I use rebar 2.5.0.<br /><br />rebar.config:<br /><br />{deps, [<br /> {C, ".*", {git, "git_path_to_dependecy", {tag, "v1.0.0"}}},<br /> {B, ".*", {git, "git_path_to_dependecy", {tag, "v1.0.0"}}},<br />]}.<br /><br /><br />What am I doing wrong? Or where can I read about dependency tracking<br />more detail?<br /><br />Thanks in advance.<br /><hr /><br />erlang-questions mailing list<br />erlang-questions@erlang.org<br /><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a><br /></pre></blockquote></div></body></html>