Bryan Paxton

Hi, I think the problem here is the docs aren't clear enough : ``` {hex, [ {repos, [ #{name => , api_url => , repo_url => } ]} ]}. ```...

@tothlac Right, the form has to be : ``` {hex, [ {repos, [ #{name => , api_url => , repo_url => } ]} ]}. ``` Edit: This is old and...

So, something like this in this case? ``` ===> Invalid hex configuration found. Expected a property list, got : {doc,#{provider => edoc}} ``` Maybe we could spit out some info...

> We do need to abort if we can't figure out what repos to use. yeah, that would be this case specifically, because hex config was not a proplist, thus...

> A quickfix might be to swap the order and make the rebar3 regular apps build first, but we create the opposite scenario: if an Erlang app is trying to...

> uh so that lib both needs to be compiled before and after lager at the same time to work? Or it's just that it badly declared its dependency? Nah,...

> It looks like logger_lager_backend is being compiled without lager being in the code path. Disabling tracing will not work because if it's a compile time dependency it would fail...

@ericmj Yeah, I was just demonstrating how the code path is in place. Maybe you're thinking it can't find the source for lagger?

As to why we get `warning: :lager.dispatch_log/7 defined in application :lager is used by the current application but the current application does not directly depend on :lager. To fix this,...

Only other thing would be sorting out conflicts, not sure that's a concern for rebar. I assume the support in mix for `or` here is in case one dep wants...