Starting riak_core as application, how-to

[djui]

Hej,

I was wondering if the riak_core_util:start_app_deps(riak_core) in riak_core_app:start/2 isn't creating a chicken'n'egg problem? When I try to start riak_core (for testing) from a shell by application:start(riak_core), it throws exception because the other applications (crypto, webmachine) are not running yet. So the code of start_app_deps/1, which itself uses the same app file key as ERTS for getting a list of applications is never reached. And when starting the deps applications before, there is no use for it.

So I wonder if I missed something when starting the riak_core app up. I currently use:

erl -pa ebin deps/*/ebin \
    -boot start_sasl \
    -eval "application:start(crypto), application:start(webmachine), application:start(riak_core)."

[rzezeski]

This is interesting. For a Riak deployment the bootscripts should be starting all the applications and in the appropriate order. If just messing with core at a console then I don't see how this works at all because the applications will be returned in the wrong order and when ensure_started calls application:start it will {error,{not_started,foo}} and cause a badmatch. Although, in practice, when I run application:start(riak_core) I don't see a badmatch.

I'm not sure why this code is needed at all and I don't think it should be called by riak_core_app:start.

[jrwest]

closing this out. perhaps there is an issue here but after working on two separate core applications (riak and other application for previous employer) booting applications has not been an issue. If the issue still applies today please create a new one.