A problem was found with the configuration of task ':spotlessJavaCheck'. /build/spotless/spotlessJava' specified for property 'spotlessOutDirectory' does not exist.

[compilead]

If you are submitting a bug, please include the following:

• summary of problem
  Task :spotlessJavaCheck FAILED
  What went wrong:
  A problem was found with the configuration of task ':spotlessJavaCheck'.
  Directory '......./build/spotless/spotlessJava' specified for property 'spotlessOutDirectory' does not exist.
• gradle or maven version
  gradle-5.6
• spotless version
  spotless_version = '5.8.2'
• operating system and version
• copy-paste your full Spotless configuration block(s), and a link to a public git repo that reproduces the problem if possible
  spotless {
  format 'misc', {
  target '/*.gradle', '/.md', '/.gitignore'
  trimTrailingWhitespace()
  indentWithSpaces()
  endWithNewline()
  }
  java {
  target project.fileTree(project.rootDir) {
  include '/.java'
  exclude 'build/generated/**/.'
  }
  googleJavaFormat().aosp()
  }
  }
• copy-paste the full content of any console errors emitted by gradlew spotless[Apply/Check] --stacktrace

If you're just submitting a feature request or question, no need for the above.

[compilead]

Because of this Pipeline stage is failing for code format check... can anyone help me resolving this issue.

[nedtwigg]

Dupe of #741, fixed in 5.9.0 (you are using 5.8.2)

[compilead]

Hi @nedtwigg,

Even after updating spotless version to 5.9.0 we are getting following issue:

Task :spotlessJava
Exception caught during execution of command '[<>/git/2.22.0/bin/git, config, --system, --edit]' in
'/<>/git/2.22.0/bin', return code '128', error message
'fatal: Invalid path '/<*>/git/2.22.0/etc': No such file or directory

There is no directory etc. I am confused is it related to soptless or what ?

[nedtwigg]

That's a very strange error trace. Maybe try --stacktrace?

[compilead]

when i run command >> ./gradlew --stacktrace spotlessJava getting following op:
BUILD SUCCESSFUL in 968ms
1 actionable task: 1 up-to-date

[nedtwigg]

Huzzah, it's fixed! ;-) If you would like further help, it's easier to read your debuginfo if you read this. As of now, it looks to me like 5.9.0 did in fact fix the issue. If that isn't true, please provide well-formatted, readable details.