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
Merge jjohannes/missing-metadata-guava into this plugin #2
Comments
Thanks for the feedback! Will give this give this some thoughts (also related to #1). |
I think I would like to do this for a potential |
missing-metadata-guava covers two aspects compared to the other rules in this plugin:
The first fits perfectly in here. The second is a bit different compared to other rules and is strictly not directly about Capabilities only. But it is very related so I think it fits in here as well. |
Setting both JVM Version and JVM Environment do different values (which are mostly compatible) creates to much ambiguity for Gradle to make a clean/good selection in some case. JVM Environment is the important bit. Related to #2
Setting both JVM Version and JVM Environment do different values (which are mostly compatible) creates to much ambiguity for Gradle to make a clean/good selection in some case. JVM Environment is the important bit. Related to #2
Looks like https://github.com/jjohannes/missing-metadata-guava is related, and the name of
java-ecosystem-capabilities
sounds good for an umbrella project.The text was updated successfully, but these errors were encountered: