-
Notifications
You must be signed in to change notification settings - Fork 255
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
Investigate dependency resolution issue with JUnit #82
Comments
I'd say updating the dependency (to 1.2.5-SNAPSHOT) is the best thing to do, and then bump to 1.2.5 as soon as it is available. |
Dependency divergence in the minor part of the version number, for test scoped dependencies, doesn't seem any problem to me? Otherwise we would be writing |
Option 2 appears to be impossible, as
|
Cucumber 1.2.5 has been released and uses JUnit 4.12 |
We probably need to see if there again problems with the adoption of JUnit 5 per #99 |
Thanks! We're using Cucumber 1.2.5 now, and it works. It does still rely on good old JUnit 4 and its RunWith extensions at the moment, but that works. |
There appears to be a dependency resolution issue with JUnit. Cucumber 1.2.4 requires JUnit 4.11, whereas the framework requires JUnit 4.12.
There seem to be two possible solutions:
Bump cucumber to version 1.2.5-SNAPSHOT which does depend on JUnit 4.12 (originally junit 4.12 broke compatibility with android)See Investigate dependency resolution issue with JUnit #82 (comment)The text was updated successfully, but these errors were encountered: