1. 8

Rebar3 is a major departure from previous versions of the rebar build tool. So much so it will feel like a new build tool all together. Because of this we’ve put together a collection of blog posts about some of the new features that we think will entice you to make the switch:

Plus a couple posts about particular plugins:

More posts will come over time as we head to a stable 3.0 release, including eunit, common test, dialyzer and the unique features of rebar3 shell.

  1.  

  2. 1

    For those of us who don’t write Erlang code regularly, is it possible to summarize the bent of the changes? Glancing through these changes, it seems like the main reasons for breaking backwards compatibility was repeatability and extensibility?

    1. 1

      Correct. To make repeatability and extensibility more natural the entire “core” had to be replaced. In previous rebar’s it acted more like Make, it would cwd in to subdirectories and check ‘what can I do here’ and do it. Now we construct an entire view of the project and its dependencies from the top level and go from there.