Make default riak services and console configurable in rt.erl #752
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #260 I had another change to riak_test I needed to perform, following
@Licenser's blog article to adapt it to my current riak_core based project. This PR reflects
that change. In summary it
The defaults remain unchanged so there should be no breaking introduced.
With this change it should be possible to precompile a self contained riak_test escript and
include it in a project in much the same way as rebar or relx. In this way the riak_core based
project can provide its own rt_harness and configuration and will have a reduced need to use
a forked version of riak_test. @loucash is already using riak_test a compiled escript and this
works well for his project.
A PR based on or derived from this PR would allow us to whack our riak_test forks and use
basho's riak_test vanilla out of the box without changes.
FYI @cmeiklejohn - The only difference when compared to the lasp usage of riak_test would be using a self-contained riak_test escript to drive the tests rather than a local installation. So we may even be able to run riak_test under travis!