-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop 3.0 mergerebar3 #248
Conversation
…thumbs targets succeed.
…tructure - relative paths no longer cut it.
…ut EQC. - Expands the list of Thumbs build steps for better coverage. - Adds actual application dependencies to .app.src for dialyzer goodness. - Adds missing record field type specs, also for dialyzer. - Cleans up remaining edoc errors.
…update git's merge pointer to avoid conflicts later.
Needs to produce script as expected by riak make rel
We have thumbs no more
I think cuttlefish is being pulled in (when making a release) from the kyorai fork via the rebar3_cuttlefish plugin, so we may need to bring that inline and merge with this at some point. |
It is @martincox branch of https://github.com/martinsumner/rebar3_cuttlefish/tree/develop-3.0 Will PR this into the basho version today. |
Ahh sound then 👍 |
There was some work to tidy up cuttlefish in Ted's rebar3 branch. This work was required by the bitcask develop-3.0 branch to run its bitcask schema check unit tests.
I've merged in here, but ignoring most of the rebar.config changes (as the rebar3 branch didn't escriptize as expected a cuttlefish file).
There is an update to a
cuttlefish_rebar_plugin
module - to make it rebar2 not rebar compatible - but this is not yet rebar3 compatible. I can't see anything using this module - so the lack of rebar3 support is hopefully not an issue.