-
Notifications
You must be signed in to change notification settings - Fork 459
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
Gradle plugin 6.6.1 introduces conflicting variant "spotless123" #1215
Comments
Thanks for reporting this bug. I think you can workaround it with a spotlessPredeclare block. |
I tried the |
Ran into the same issue w/ latest spotless plugin version 6.8.0 in another way (projectnessie/nessie#4655). The change that caused the issue to happen was an unrelated dependency version bump. |
See projectnessie#4655, required until diffplug/spotless#1215 is fixed. Similar to projectnessie/cel-java#185.
See projectnessie#4655, required until diffplug/spotless#1215 is fixed. Similar to projectnessie/cel-java#185.
See #4655, required until diffplug/spotless#1215 is fixed. Similar to projectnessie/cel-java#185.
Run into the same issue, and for some reason, the spotlessPredeclare extension is not available to check if it works on my issue. My root project has a custom name, maybe that is the reason Spotless is not generating the extension. |
Fix published in |
Since diffplug/spotless#1215 has been closed, a few Github workflow steps can be simplified.
Since diffplug/spotless#1215 has been closed, a few Github workflow steps can be simplified.
(See also projectnessie/cel-java#185 )
Steps to reproduce:
./gradlew check
-> failure./gradlew assemble check
works (may want to add-x jmh
to skip running the microbenchmarks)Downgrading the spotless plugin (in
settings.gradle.kts
) to 6.6.0 "fixes" the problem.CEL-Java uses the Gradle
rootProject
for dependency management, as that's the easiest way that also works with dependabot.So submodules use
platform(rootProject)
for pull in dependency versions.This started to fail with the Spotless Gradle plugin 6.6.1.
It seems that the temporary configurations ("spotless123...") leak variants that are too similar to "regular" variants and cause the conflict. Probably due to some daemon-leak fix in 6.6.1 that causes (too?) eager configuration/variant creation.
The text was updated successfully, but these errors were encountered: