Roll dependencies for 1.4.2
Setup develop branch
Update riak_search to support some new core apis

Specifically, handle the removal of riak_core_config and the switch to
v2 riak_core fold requests by also handling v1 fold requests.
Merge pull request #150 from basho/adt-api-updates

Update riak_search to support some new core apis
don't forward folds in handle_handoff_command; do upgrade properly in handle_command

This is related to basho/riak#407. The old fold_req needs to be caught and
upgraded properly, instead of forwarded.
Merge pull request #151 from basho/bugfix/bwf/fold-req-upgrade

don't forward folds in handle_handoff_command; do upgrade properly in handle_command
Standardize on a rebar.config dep format to reduce conflicts
Fix build now that riak_core_pb.hrl is in riak_kv
added {enabled, false} to app.src
Merge pull request #153 from basho/jd-enabler

added {enabled, false} to app.src
Fix search tests

Host/port was changed from being a riak_core config to a riak_api config
a little while ago.
After the default setting for allow_mult (return siblings) was changed,
search has been unhappy as it relied on it. This change enforces the old
default in search buckets to allow it to exist in this brave new world
Merge pull request #154 from basho/bugfix/search-allow-mult-fallout

Fix search tests
Bump riak_kv dep to 1.4.4
Point to riak_kv 1.4 branch for now
Don't start riak_search is security is enabled
Set riak_kv dep at 1.4.4
Merge pull request #156 from basho/adt-security-holes

Don't start riak_search is security is enabled
Update riak_kv dep to 1.4.5
Update riak_kv dep to 1.4.6
Allow search to start if security is enabled, just disable its APIs

It turns out that simply not starting search if security is enabled did
not play well with the new 'riak-admin security enable' command, because
it was decoupled from node startup. Instead, simply disable the endpoint
APIs that search exposes if security is enabled, making it more friendly
to runtime changes.