Separate projects have separate custom rules lists configured.
If you configure (add) a custom ruleset in one project, you open another project and want to run pmd, it is not in the action menu, to run pmd with the custom rule set.
This is a kind of unexpected, you have to configure it again, per project.
To make this easier, the action menu is merged from all open project configurations, and you don't have to re-configure; only once instead. This also gets back from the action menu to configuration.
However, if you add several rulesets, they stick around. They get propagated from one to others and deleting in one configuration does not help, it comes back when merged and the list can only grow.
Best solution would probably be to configure on singleton/central level instead on project level.
Easier solution is to remember deleted ones and remove them when merging.
jborgers
commented
7 months ago
Separate projects have separate custom rules lists configured. If you configure (add) a custom ruleset in one project, you open another project and want to run pmd, it is not in the action menu, to run pmd with the custom rule set. This is a kind of unexpected, you have to configure it again, per project. To make this easier, the action menu is merged from all open project configurations, and you don't have to re-configure; only once instead. This also gets back from the action menu to configuration.
However, if you add several rulesets, they stick around. They get propagated from one to others and deleting in one configuration does not help, it comes back when merged and the list can only grow.
Best solution would probably be to configure on singleton/central level instead on project level. Easier solution is to remember deleted ones and remove them when merging.