-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Enable Rebar 3 support by default #4042
Comments
Issue opened on rebar3: erlang/rebar3#958 |
Note for myself: we also need to verify that rebar3 does not evaluate |
I believe this has been enabled for a while, right @ericmj? |
It has been :) |
We still need to make rebar3 the default package for Git dependencies. |
What do you think about introducing a warning if |
I'm having trouble compiling the hex package "cf" v0.2.1 with an elixir/mix build from current master and the latest hex and rebar3 installed (from hex). I don't know enough about rebar3 to know if it's the package's fault or not, but it works fine on Elixir 1.2.5. |
You can pass manager: :rebar2 to your dependency options. Does it fix the On Wednesday, May 18, 2016, Eric Entin notifications@github.com wrote:
José Valimwww.plataformatec.com.br |
"cf" is listed as a rebar3 project on hex. But without any more information it's impossible for us to say what is going on.
It should be |
"cf" does work when the manager is overridden to
|
Here's the rebar3 report for the command, as well:
|
@antipax update erlware_commons from 0.19.0 to 0.20.0 this fixes error for Uncaught error: {badmatch,
{error,
{19,file,
{error,
{badmatch,
["3","0","0+build","272","ref7d29b74"]},
[{erl_eval,expr,3,[]}]}}}} I had the same issue, it will be fixed with: |
The issues above with @josevalim Wdyt about this:
|
When would this happen? |
@ericmj ping. :) Btw, I think we should make rebar3 the default in master so we can give it a try for a good while. |
I pushed a change to master that detects |
Implemented in 17557aa. |
Before we make this work, we need to find a way for Rebar 3 to not prompt for registry updates repeatedly.
The text was updated successfully, but these errors were encountered: