Eric Meadows-Jönsson
Eric Meadows-Jönsson
Do you think there is a way forward to at least improve some things in this area? Maybe push some of the functionality plugins provide into deps so that plugins...
> Only needed after deps are fetched if there isn't a plugin that uses the compiler ;) Wouldn't the plugin have the compiler as a dependency if it required it?...
It looks like logger_lager_backend is being compiled without lager being in the code path. Disabling tracing will not work because if it's a compile time dependency it would fail to...
I think I am missing something. If removing the code path triggers `warning: :lager.dispatch_log/7 is undefined` then don't remove it.
> [...] removing this definitely triggers `warning: :lager.dispatch_log/7 is undefined (module :lager is not available or is yet to be defined)` I am saying that if removing the code path...
If the compiler automatically fetches the registry or if mix can pass the path of its own registry to rebar works for me.
Another option would be for mix to treat plugins as normal dependencies so we fetch. In this case they should be available when rebar runs and fetching the registry would...
With the bare compiler rebar assumes that the user have provided all dependencies and that they are correct so rebar should not need the registry to proceed.
If possible the way I would like plugins to be handled would be that I make sure the plugins rebar need are available in the code path the same way...