Closed benoitc closed 1 year ago
You have to call rebar3 as global plugins upgrade rebar3_hex
Thanks that worked. That's not very intuitive though :) Why does it try to upgrade the plugin in the debug log if it will not install it to be used?
Do you happen to have the plugin both local and global at the same time?
As for the intuitiveness: it's because we never designed for global plugins to be a thing, we initially thought only local ones made sense. People kept asking for the global ones, so we ended up adding them (it made a lot of sense for templates and per-workplace custom commands), but there was nothing in our design that allowed for their upgrade to be handled with the expected commands. The global profile was a sort of magic command hack we came up with as a compromise and it stuck since then.
Can we open up an issue on rebar3 for this? If there's not already one open...
Closing this as stale. Please re-open if you feel otherwise.
I am running latest rebar3
And trying to upgrade the plugin
rebar3_hex
:By running the command line
DEBUG=1 rebar3 plugins upgrade rebar3_hex
but rebar3 keeps returning the 6.11.4 version of it in the list of plugins (rebar plugins list
).The result of the upgrade: