This is definitely a bug. Please raise it in Jira.
I've got a fix ready to go. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ <[EMAIL PROTECTED]> wrote on 18/11/2003 02:59:28 AM: > > I'm producing a PMD report on my code, but I want to exclude some > classes that are generated by JavaCC, because it makes code analysers go > nuts. Just one parser produces two thousand violations... It seems that > a single exclusion pattern works fine, but as soon as I put in a comma > separated list all the exclusions are ignored. For example: > > maven.pmd.includes=com/foo/project/**/*.java > maven.pmd.excludes=com/foo/project/package/SomeParser*.java > > works fine, analysing everything except the SomeParser classes. However, > > > maven.pmd.includes=com/foo/project/**/*.java > maven.pmd.excludes=com/foo/project/package/SomeParser*.java, > com/foo/project/package/ADifferentParser*.java > > causes the analyser to match as though only maven.pmd.includes was > specified. > > Any ideas here, or should I head off to JIRA? > > Cheers, > > Nick > > --- > Research Engineer > Intelligent Systems Lab, BT Exact > Tel: (+44)1473 605 894 > Email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
