Including Rebar3 in official Erlang/OTP releases

By Industrial Erlang User Group | Published: October 22, 2015

The Industrial Erlang User Group and Ericsson have discussed the possibility of including Rebar3 in the official Erlang/OTP releases and made progress.

In a recent monthly meeting between IEUG and Ericsson, the Industrial Erlang User Group expressed its intention of endorsing Rebar3 as a build tool and package manager and releasing Rebar3 together with the official Erlang/OTP. Ericsson is positive about including and endorsing Reber3 in the OTP releases, as long as certain changes are made in Rebar3.

The proposed changes mainly concern issues such as third party dependencies, improved usability and improved workflow between the OTP team at Ericsson and the Rebar3 team. The IEUG and Rebar3 team are working closely to address the changes proposed by Ericsson. As a result, the IEUG will not develop a new package manager client from scratch at this moment, with regard to existing competing tools in Erlang.

Proposed changes to Rebar3 include, but not limited to, the following:

1. Rebar3 dependencies need to be reduced. A resolution is needed for each of the third party dependencies.

2. Additional requirements to Rebar3:

  1. There should be a command to let users see a package’s information e.g. dependencies.
  2. There should be a command to let users download package files without compiling and installing the code.
  3. Rebar3_hex plugin to use Erlang terms instead of JSON

3. Further discussion is needed about the location where rebar3 will be placed. One option would be to move it to, while released in OTP releases.


About Industrial Erlang User Group

The Industrial Erlang User Group is a non-profit organization consisting of a group of enterprise Erlang users, funding a range of activities focused on developing the Erlang community and broader adoption.


For more information, please contact

Bruce Yinhe, Community Manager, tel: +46 72 3114389, email: community-manager (@)

Follow Erlang Central:

Have an Erlang Question?

Reach out to the Erlang community