We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the library au.com.dius.pact.provider:junit5spring publishes with runtime scopes for all the transitive dependencies: https://repo1.maven.org/maven2/au/com/dius/pact/provider/junit5spring/4.1.12/junit5spring-4.1.12.pom
au.com.dius.pact.provider:junit5spring
Gradle doesn't fetch it as it transitive and it forces library-consumers to explicitly declare au.com.dius.pact.provider:provider:junit5.
au.com.dius.pact.provider:provider:junit5
Maven does. That's why maybe this is not changed yet.
This is the only library with these scopes, for instance provider:junit5 is okay and transitives have compile scope.
Is there a reason for it? Please align it, I hope to compile side. Or let's update documentation
compile
The text was updated successfully, but these errors were encountered:
chore: change the scope of deps to api #1280
6a94e2c
4.1.13 released
Sorry, something went wrong.
Thanks! Scopes are okay now
No branches or pull requests
Currently, the library
au.com.dius.pact.provider:junit5spring
publishes with runtime scopes for all the transitive dependencies: https://repo1.maven.org/maven2/au/com/dius/pact/provider/junit5spring/4.1.12/junit5spring-4.1.12.pomGradle doesn't fetch it as it transitive and it forces library-consumers to explicitly declare
au.com.dius.pact.provider:provider:junit5
.Maven does. That's why maybe this is not changed yet.
This is the only library with these scopes, for instance provider:junit5 is okay and transitives have compile scope.
Is there a reason for it?
Please align it, I hope to
compile
side. Or let's update documentationThe text was updated successfully, but these errors were encountered: