Replies: 1 comment
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
We have used spotless for quite a while now on the WireMock project. We use it to format files in the project and apply a license header (with a year or year range) to source files that are new or have changed.
We have recently started to see builds fail due to spotless thinking some of our java files need the license header updated to have a
2025
year in the header. The strange thing is that the files that it is failing on haven't changed. I have even see themain
build fail when the branch I just merged all passed. We are seeing the failures on our Windows java 17 builds (we build on java 11 and java 17 across mac os, ubuntu and windows)You can see in this PR that only one file has changed but the build is failing. The failure is:
We have updated to the latest spotless recently (
id 'com.diffplug.spotless' version '7.0.2'
) but I haven't yet correlated whether the issues started at the same time or not.We use gradle for our builds with the following config:
Is anyone else experiencing similar issues?
Beta Was this translation helpful? Give feedback.
All reactions