Rebar3 support and code sharing

Yeah, the alternative is to print a warning to let the user know both dirs
exist and are going to be used.

On Sat, Oct 11, 2014 at 11:47 AM, Tristan Sloughter <
notifications@github.com> wrote:

> In src/rlx_prv_discover.erl:
>
> > @@ -105,7 +118,7 @@ add_common_project_dirs(State) ->
> >                                      false ->
> >                                          LibDirs
> >                                  end
> > -                        end, [], [Deps, Lib, Apps, Ebin])
> > +                        end, [], [Rebar3Deps, Deps, Lib, Apps, Ebin])
>
> I'd almost say I agree except relx seems to already be based around the
> idea that it will search everywhere to find apps to resolve your release.
> So in the case of relx I think it may be expected to search both. And
> since neither are hidden dirs it is less likely the user will be confused.
>
> Probably something we'll want to revisit when/if people start using rebar3.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/erlware/relx/pull/227/files#r18742562>.
>