This bug https://sourceforge.net/p/pmd/bugs/1079/ was closed on August 11 2013. My plugin has the same date, but I feel like it's ignoring the <exclude-pattern>. The 5.0.5 release was done the same day, but I feel that this fix is not in it (from looking at the 5.0.x branch).</exclude-pattern>
Can someone confirm it? Can someone release new plugin build with that in it? It's a pretty serious problem for us.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it might be a minor bug mixed with user mis-understanding. I got a bunch of violations for generated source. I added the exclude-pattern. The violations still were there (even after doing an explicity "Check Code"). But, if I manually remove the violations they don't come back.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hm... I'm not sure, when the eclipse plugin clears the violation. You can clear all violations manually and the do "Check Code" again.
Maybe this violations clear should be triggered automatically when the exclude pattern is changed?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This bug https://sourceforge.net/p/pmd/bugs/1079/ was closed on August 11 2013. My plugin has the same date, but I feel like it's ignoring the <exclude-pattern>. The 5.0.5 release was done the same day, but I feel that this fix is not in it (from looking at the 5.0.x branch).</exclude-pattern>
Can someone confirm it? Can someone release new plugin build with that in it? It's a pretty serious problem for us.
Hi,
this was actually a bug in the eclipse plugin - not in PMD.
The eclipse plugin is released from master and not a branch.
The commit is this one: https://github.com/pmd/pmd/commit/acc799e79dc66f6c55eb6e55637b3411c425787c
If you feel, that it is not fixed - please reopen the bug and attach the ruleset file with the exclude pattern, that don't work.
Thanks,
Andreas
I think it might be a minor bug mixed with user mis-understanding. I got a bunch of violations for generated source. I added the exclude-pattern. The violations still were there (even after doing an explicity "Check Code"). But, if I manually remove the violations they don't come back.
Hm... I'm not sure, when the eclipse plugin clears the violation. You can clear all violations manually and the do "Check Code" again.
Maybe this violations clear should be triggered automatically when the exclude pattern is changed?
That's how I see it. What I called a "minor bug".
I've created a bug for this: [#1148]. It's fixed with the new release.
Related
Issues:
#1148