diffplug / diffplug/spotless

Groovy formatting with Spotless leaves a temporary directory

Aperta
#2,019 6 commenti 7 reazioni 0 assegnatari Vedi su GitHub
bug
Lingua principale
Java
Stelle
5.6k
Fork
559
Merge medio
1g 14h
PR unite (30g)
43

Descrizione

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

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
groovy, java
Ambito
build-system, tooling
Tipo di issue
Bug
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
50/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.