mix: Don't depend on eqc_ex in production builds #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1.3.0 contained errors in their mix.exs, which results in no eqc subcommands being available through mix. These issues were solved in 1.3.1. Reference: Quviq/eqc_ex@cd37425
|
Also note: the latest eqc_ex version is 1.4.2; that works to. I've managed to run the tests with both eqc_ex 1.3.2 and 1.4.2. Should I bump it to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #7
Edit: I've also decided to add another change to this pull request to avoid merge conflicts:
Bumping the dependency for eqc to 1.3.1. I think syntax errors in the mix.exs file causes mix to not register the eqc subcommands (they don't appear in
mix help, etc). I hope I managed to bump the version reasonably, both in mix.exs and in the lock.file, but please verify that it works for you as well. You will end up with 1.3.2, but only becuase that's the most recent version compatible with~> 1.3.1.