mustache:render("{{banan}}", dict:from_list([{banan, true}])).

** exception error: no function clause matching mustache:escape(true,[])
     in function  erl_eval:do_apply/5
     in call from erl_eval:expr/5
     in call from erl_eval:expr/5
     in call from mustache:render/3

- Check the existence of first_files and fail if they are not present
 - Get first_files lists from local instead of inherited config
   definitions, since they only make sense in the local context

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.