Generated by 🚫 Danger

The way I understand the ticket #4187, it's about rendering an arbitrary user ruleset in a fully explicit form, to show how PMD understands it. I imagine a pmd resolve-ruleset command could be written directly with the existing RulesetWriter with little effort. OTOH this PR implements a more specific solution, and tbh I'm not convinced it's desirable to pregenerate rulesets with all rules like that... I would prefer not to encourage users to enable every rule they can -that's why we have the quickstart rulesets, and partly why we split categories from rulesets.

A utility to explicitize rulesets could technically also be used to implement the same thing you do in this PR (pmd resolve-ruleset rulesets/internal/all-java.xml) but it would be more generally useful, eg in the case of #4187 where OP wants to check what changed in their ruleset specifically. Another use case is to communicate with eg a future PMD ruleset editor GUI, which I believe we talked about to prepare gsoc a few years ago.

Let's move this for now at least to 6.53.0 - I won't have time to continue working on this.

Agreed - it won't fix the original issue (#4187) - that's why these are not linked. It could serve as a viable workaround. Not sure if it's worth continuing this path. However, you only get feedback, once it's out there. We could create it in 6.53.0 as experimental and remove it again in 6.54.0 if we get negative feedback or no feedback at all...

I'm closing this as won't fix. We should consider a solution together with #4295 after PMD 7 is out.