Skip to content
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

Spotless is leaking Java 11 dependency. #1032

Closed
JavierSegoviaCordoba opened this issue Dec 11, 2021 · 2 comments
Closed

Spotless is leaking Java 11 dependency. #1032

JavierSegoviaCordoba opened this issue Dec 11, 2021 · 2 comments

Comments

@JavierSegoviaCordoba
Copy link
Contributor

JavierSegoviaCordoba commented Dec 11, 2021

Summary

I have a published plugin that is configuring Spotless and I apply it in all my projects, after upgrading Spotless to 6.0.3, My project, which is Java 8, which is applying my published plugin can't be compiled because of a dependency is Java 11.

The consumer was configured to find a runtime of a library compatible with Java 11, 
packaged as a jar, preferably optimized for standard JVMs, and its dependencies 
declared externally, as well as attribute 'org.jetbrains.kotlin.platform.type' with 
value 'jvm'. However we cannot choose between the following variants of project :mokoki-core:
    - jvmRuntimeElements
    - spotless1316845943

spotless1316845943 this should not be appearing there I think, but it is being leaked into the project.

I am not having this issue with 6.0.2, but 6.0.4 has this issue too, not only 6.0.3.

  • Gradle 7.3.1
  • Windows 10

My published plugin is adding Spotless as a dependency (implementation(...)). So the consumer hasn't to add Spotless to the classpath itself, because the plugin has the dependency directly.

@nedtwigg
Copy link
Member

Related to #1027

@nedtwigg
Copy link
Member

Should be fixed in 6.1.0, please reopen if the issue persists. See these docs for more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants