I see what the trick is here. When running in eclipse, the existing scheme plays a trick to use set of PMD rules that omits the custom rule, for the very reason you ran into. Unfortunately for us, the auto-configuration tries to pick them right back up, but that does not fly.
So, the question is, how to derail this? One way is to define a profile that redirects the PMD rules in the eclipse case. I'll have a look.
