Using rebar's commandline, enable/disable 'debug_info' for
compilation. This feature if added to all rebar compilers could help
simplify and standardize this common use case for all rebar build
targets.

e.g. {dialyzer_opts, [{plt, "~/.dialyzer_plt.R14B"}]}.

Use rebar_utils:find_executable/1 that wraps the
path in quotes to make it work even if it contains
whitespace.

Change git downloads and updates to not create branches and fix git
tag handling.

If rebar tries to clean the .app file (because there's a .app.src file)
and it doesn't exist (possibly because of a bad compile), don't fail.

Make the error message newline terminated and, if possible, log the name
of the module in which the failure occured.

Modify rm_rf and cp_r to work when {win32,_} = os:type().
Simplify rm_rf to only accept one filename, directoryname or wildcard.
Add unit tests to ensure a similar behaviour on windows and unix.

Thanks to tuncer for guidance and feedback.

mkdir_p/1 and ln_sf/2.

Add support for invoking rebar from other than current directory.
For example: ..\rebar create-node nodeid=mysample

requires rebar.bar and rebar (escript) to be in the same directory.

If there is no convention or way to programatically figure out what files to process, don't guess.

--HG--
extra : rebase_source : 466f440dcb

The eunit_dir() does use the ?EUNIT_DIR macro internally, but it also builds, what I guess is, an absolute path, which might be better :) At least it's more consistent.

Normally the ebin directory doesn't contain any source files. Therefore it won't be kept in the repository by, at least, mercurial and also maybe git unless you put some .keep file in it or do some other hack. The ebin directory is created by rebar compile, but if rebar eunit is called before rebar compile, you end up with a {'EXIT', {{badmatch,{error,bad_directory}},...}. Another approach would be not to match cod:add_pathz(ebin_dir()) with ok, but I think this is an ok solution as well.

Thanks to Kostis for no_return() result type.

Thanks to Cliff Moon for correct fun clause to add.

The previous code in rebar that was trying to ensure that parse
transforms and behaviours were compiled first doesn't work with multiple
compiler workers because of the possiblity of one of the workers
compiling a file that needs a parse transform or a behaviour at the same
time another worker is compiling that same parse transform or behaviour.

The solution this patch implements is to append any parse transforms and
any behaviours (in that order) to erl_first_files to ensure that they
are compiled before any regular files. This patch won't break any
currently working uses of erl_first files because we only append to the
list, so anything in erl_first_files is still compiled before anything
else.

Add a coverage report similar to the one output to index.html except
that it is output to the terminal if the new rebar.conf option
'cover_print_enabled' is set to true.

Ignore common files during development.

Ignore common files during development.

Signed-off-by: Essien Ita Essien <essiene@gmail.com>
---
 .gitignore |    7 +++++++
 .hgignore  |    1 +
 2 files changed, 8 insertions(+), 0 deletions(-)
 create mode 100644 .gitignore

The previous fix to relax the regex was insufficient.
This is basically the diff proposed by Bryan Fink with
the difference of using 'C' instead of 'en_US'.

Reported-by: Manuel Duran Aguete <manuel@aguete.org>