Absolutely! This was only about palantir, the java formatter. Spotless (the plugin running palantir) can also do XML etc., so we can keep that! :)
At work, I have the format goal in validate or initialize phase or so, the CI runs `mvn spotless:check` before running `mvn verify` -- this way, clean code (pom.xml etc.) is ensured. Am Mo., 30. Dez. 2024 um 10:06 Uhr schrieb Matthias Bünger <runningj...@web.de.invalid>: > > > Am 30.12.2024 um 08:55 schrieb Guillaume Nodet: > > Le dim. 29 déc. 2024 à 16:12, Benjamin Marwell <bmarw...@apache.org> a > > écrit : > >> We could instead configure checkstyle to make sure the style is as > >> intended. > > I'd rather remove all rules, than going back to a state where we have > > very strong > > rules without any easy way to apply them. > > When you write/modify a few lines of code, it's ok. But when dealing with > > large > > code changes, the time spent on formatting the code is way too high compared > > to the value of having strict rules imho. That's why automatic > > formatters are nice > > tools. > > I would also like to have formatter for other file formats, e.g. XSD, > XML, APT etc. Even when I only passivly apply the 120 chars per line via > auto-save-formatting I get tons of changes, cause tons of files are not > formatted according to style conventions. > > This mostly results in me reverting everything and redo it without > auto-formatting so the PR only has the "real" changes (which on the > other side is violates camp-site-rule :/ ) > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
