| commit | 4802c0a6cac1aae2a6fc43a57d6cbd5c09fc4050 | [log] [tgz] |
|---|---|---|
| author | Luis Rascão <luis.rascao@gmail.com> | Fri Feb 12 13:15:30 2016 +0000 |
| committer | Luis Rascão <luis.rascao@gmail.com> | Mon Mar 14 12:06:28 2016 +0000 |
| tree | b54fc2a2a59f99095cd1b15c069408c26190b079 | |
| parent | 13a570ed93220564460562e07fda9d90a0dd18dd [diff] |
Optionally look for ct .spec files in the ct_dir that was specified
Allow to change existing behaviour which is to find all .spec
files recursively in the current working directory through a new
rebar.config option: {ct_search_specs_from_test_dir, true}
This is confusing since the user explicitly stated the
location for his spec files and negates the possibility
to have different spec'ed suites for different environment.
Also fix the node name generation on the ct test run, append
a random number that will reduce chances of name collisions
on epmd.
rebar is an Erlang build tool that makes it easy to compile and test Erlang applications, port drivers and releases.
rebar is a self-contained Erlang script, so it's easy to distribute or even embed directly in a project. Where possible, rebar uses standard Erlang/OTP conventions for project structures, thus minimizing the amount of build configuration work. rebar also provides dependency management, enabling application writers to easily re-use common libraries from a variety of locations (git, hg, etc).
Information on building and installing Erlang/OTP can be found here (more info).
To build rebar you will need a working installation of Erlang R13B03 (or later).
Should you want to clone the rebar repository, you will also require git.
You can download a pre-built binary version of rebar from:
https://github.com/rebar/rebar/wiki/rebar
$ git clone git://github.com/rebar/rebar.git $ cd rebar $ ./bootstrap Recompile: src/getopt ... Recompile: src/rebar_utils ==> rebar (compile) Congratulations! You now have a self-contained script called "rebar" in your current working directory. Place this script anywhere in your path and you can use rebar to build OTP-compliant apps.
Please refer to CONTRIBUTING.
In case of problems that cannot be solved through documentation or examples, you may want to try to contact members of the community for help. The community is also where you want to go for questions about how to extend rebar, fill in bug reports, and so on.
The main place to go for questions is the rebar mailing list. If you need quick feedback, you can try the #rebar channel on irc.freenode.net. Be sure to check the wiki first, just to be sure you're not asking about things with well known answers.
For bug reports, roadmaps, and issues, visit the github issues page.
General rebar community resources and links: