There are three update sites:
http://download.erlide.org/update: contains all stable releases
http://download.erlide.org/update/beta: contains the release the will be promoted to stable once it passes acceptance tests. May be broken at times, but not for long.
http://download.erlide.org/update/nightly: contains the latest and greatest, but untested code. Use it at your own risk.
Building is done using Buckminster. This has the great advantage that the build is done inside a regular Eclipse workspace, with the regular builders for that project, and we don’t have to bother to add custom build scripts for Erlang code (that also has to use the same config as in the IDE).
For headless builds, the
org.erlide.releng project contains all the
necessary scripts and more detailed information. To drive the builds,
there are is a
Rakefile script (so you need to have jruby and rake
installed) which more or less calls Ant with
The Ant script can install Buckminster and there is also a
setup_tools.sh script that will install java, ant, otp R15 and jruby
in your home directory. (JRuby is used because it had seamless integration with Ant)
For building the update site from inside Eclipse, right-click on the
org.erlide.site project and choose
Buckminster→Invoke action. In the
dialog, specify org.erlide.site/buckminster.properties as properties
file and select
site.p2 as action.
The target is installed automatically by the scripts, if it’s not
already there. It will be put in
that it can be reused.
We have a Jenkins server set up to do automatic
http://ci.erlide.org. Here we will run automated tests and
stable releases can be published to the official update sites from here
There are a number of jobs that roughly correspond to the different build tasks.
puis published automatically to
masterare published manually by promoting the respective builds
masterand is manually started after acceptance tests.
Did you find errors in the documentation? Do you have improvements to suggest? Suggest edits!