We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are at least two warnings/errors that are confusing messages when the reason for the message is a dep being moved to a checkout:
In rebar_prv_lock if a dep is moved to a checkout it prints the same message as it does if a dep is removed from the config:
rebar_prv_lock
%% TODO: don't output this message if the dep is now a checkout rebar_utils:info_useless(OldLockNames, NewLockNames),
In rebar_prv_upgrade it prints an error if the user attempts to upgrade a dep that doesn't exis:
rebar_prv_upgrade
%% TODO: output a different error if the app is a checkout ?PRV_ERROR({unknown_dependency, Name});
If the dep is instead a checkout it should print an error saying that instead of that it doesn't exist.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
There are at least two warnings/errors that are confusing messages when the reason for the message is a dep being moved to a checkout:
In
rebar_prv_lock
if a dep is moved to a checkout it prints the same message as it does if a dep is removed from the config:In
rebar_prv_upgrade
it prints an error if the user attempts to upgrade a dep that doesn't exis:If the dep is instead a checkout it should print an error saying that instead of that it doesn't exist.
The text was updated successfully, but these errors were encountered: