Fix seth/rebar_lock_deps_plugin/issues/16. #17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Consider a directory layout like this:
The top-level
rebar.config
specifies{sub_dirs, ["rel", "apps/*"]}
,and each
rebar.config
has its own set ofdeps
.rebar_lock_deps_plugin
does not lock the dependencies specified in theapps/{lexer,parser,codegen}/rebar.config
files. This is a major issuefor certain projects of mine.
This difficulty arises because
rebar_lock_deps_plugin
apparently doesnot scan
sub_dir
directories for dependencies. Sincerebar
itselfdoes scan
sub_dir
directories for dependencies, it seems reasonableto expect that
rebar_lock_deps_plugin
would do it, too.