mirror of
https://github.com/correl/rebar.git
synced 2024-11-15 03:00:18 +00:00
d983beafe9
Rebar, when it encounters a lib_dir directive, caches the current code
path, adds the libdir(s) and returns the cached copy of the path. When
rebar has finished processing that directory, it restores the cached
path. This is problematic in the below scenario:
/(lib_dir)->G
A -> B -> C -> D -> E
\-> F -> D -> E
When rebar is finished processing B, it restores the code path to what
it was before it processed B, removing C, D, E and G from the code path.
This means when it comes to process F, neither D or E are in the code
path, so any header includes, rebar plugins or parse transforms will not
be in the code path. Without the lib_dir directive, rebar does no code
path cleanups, so everything works fine.
This change makes rebar only remove the explicit lib_dir code paths it
added and adds an inttest that replicates the above scenario.
4 lines
74 B
Text
4 lines
74 B
Text
{deps, [
|
|
{b, "1", {git, "../repo/b"}},
|
|
{f, "1", {git, "../repo/f"}}
|
|
]}.
|