Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow silencing skip warnings when fetching deps #1664

Merged
merged 1 commit into from
Nov 20, 2017

Conversation

liamjjmcnamara
Copy link

When fetching deps, if this is a clean repo there will be extensive
messages warning that dependencies which have already been fetched are
being skipped. For large projects being built and tested in a clean
environment this significantly increases the noise level of the build.

This modification adds an additional rebar option
(deps_warning_on_conflict) that will allow disabling these warning
messages. If deps_error_on_conflict is set, an error will still be
thrown. This will not change default behaviour of rebar.

There is a similar outstanding issue:
#1105
However this seems to be a push for not outputting warnings when the dep
version is the same, rather than disabling warnings altogether.

When fetching deps, if this is a clean repo there will be extensive
messages warning that dependencies which have already been fetched are
being skipped. For large projects being built and tested in a clean
environment this significantly increases the noise level of the build.

This modification adds an additional rebar option
(deps_warning_on_conflict) that will allow disabling these warning
messages. If deps_error_on_conflict is set, an error will still be
thrown. This will not change default behaviour of rebar.

There is a similar outstanding issue:
erlang#1105
However this seems to be a push for not outputting warnings when the dep
version is the same, rather than disabling warnings altogether.
@ferd
Copy link
Collaborator

ferd commented Nov 20, 2017

Sounds good to me. I'm finding it a bit risky to stop seeing conflicts, but since the default is still to warn, I don't have a problem with it. I'll see to merge today after having checked in with one of the other maintainers.

Thanks for the contribution!

@ferd ferd merged commit 26d30a9 into erlang:master Nov 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants