Groovy formatting with Spotless leaves a temporary directory
- Vorherrschende Sprache
- Java
- Sterne
- 5.6k
- Forks
- 559
- Ø Merge
- 1 T. 14 Std.
- Gemergte PRs (30 T.)
- 43
Beschreibung
Running `./mvnw spotless:apply` with spotless setup to format Groovy a temporary directory is left in the root. See the following reproducer project: https://github.com/attiand/spotless-tmp-file-issue
I would have no problem if the plugin left temporary directories in the Maven `target` directory, but it is annoying in the project root.
The file was named like this: `file%3A%2Ftmp%2Fspotless-groovy10387858394287009044%2F`
* Maven version: 3.8.4
* Spotless version: 2.43.0
* Red Hat Enterprise Linux release 9.3
* See: https://github.com/attiand/spotless-tmp-file-issue
Beitragsleitfaden
Rechercherichtung
Start by running ./mvnw spotless:apply in the linked reproducer project and inspect where the root-level temporary directory is created during Groovy formatting. Trace that behavior through the Maven and Groovy formatting integration; done means formatting leaves no temporary directory in the project root, with regression coverage for the reproducer case.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- groovy, java
- Bereich
- build-system, tooling
- Issue-Typ
- Bug
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 50/100