It looks like rebar does not always update or clone dependencies correctly.
Personally I've seen empty directories after a rebar get-deps. Andreas mentioned that a rebar update-deps didn't actually update a dependency. Something is wrong here.
All our dependencies are now managed by rebar, so it should work properly and give warning or error messages when it can't complete its task.
shouldn't this be a rebar ticket?
Well, my thoughts where like this. Rebar is part of our build process and it is our build process which fails.
so the issue is apparently that z_stdlib pulls a rebar which is too old..
The rebar.config in zotonic is faulty.
build: Rebar.config and Makefile problem. Fixes #543
mochiweb: merged master from origin f3f133bbfd580730d31a1c9cf54496708…