Pankraz76

**Subject:** Urgent: Process Over Pragmatism - Let's Align on Priorities We're facing a 90% blindspot in production, yet we're stuck debating template formalities. This makes no sense. I'm actively trying...

still broken yes, but dont seem to care that much.

- https://github.com/pmd/pmd/blob/ad71cb5a4a670bdb9d6b53d90476d0510dc14618/pmd-java/src/main/java/net/sourceforge/pmd/lang/java/internal/JavaAstProcessor.java#L154 - https://github.com/pmd/pmd/blob/ad71cb5a4a670bdb9d6b53d90476d0510dc14618/pmd-java/src/main/java/net/sourceforge/pmd/lang/java/internal/JavaAstProcessor.java#L161C43-L161C44

@adangel @oowekyala its up to the dev´s which way to choose. Of course a silent way, having aligned config, would be nice. Facing spotless covering almost everything it seems simple...

now its up to you how to continue: - update custom formation config which seems outdated - or simply go with some big players default like google or palantir. Spotless...

@adangel @oowekyala what do you think? is pmd build already fixing itself like in maven?

> adapt yes we on the same page. This is kind of an issue itself, as new dev´s should use this config as setup. Is there any chance to simple...

> This causes countless conflicts with main and with other in-flight PRs. Please adapt the formatter config to minimize changes. if config is updated it should be no problem. thats...

please check on your system and give format on your behalf. Current checkstyle config is pretty huge demanding cost of carry. Might be simple to apply **convention over configuration** what...

trying to migrate https://github.com/pmd/build-tools/blob/main/src/main/resources/net/sourceforge/pmd/pmd-checkstyle-config.xml to eclipse format.