A story about unexpected changes in riak-erlang-client dependencies

Daniil Churikov ddosia at gmail.com
Tue Apr 9 13:48:43 EDT 2013

Hello Yuri.

A while ago we faced same problem. Our solution was to fork all repositories
we depends on to our public account, fix all rebar.config of all deps to
point on our repos and update any repos manually. Also when we need to lock
deps, as you mentioned, we use rebar lock plugin and recursively lock all
deps on same commit.

View this message in context: http://riak-users.197444.n3.nabble.com/A-story-about-unexpected-changes-in-riak-erlang-client-dependencies-tp4027582p4027594.html
Sent from the Riak Users mailing list archive at Nabble.com.

More information about the riak-users mailing list