Re: PMD report plugin fails the build
Have you run with -U to get the latest version of the plugin? This used to happen to me, but stopped recently after running "mvn site -U" -Stephen On 8/9/06, Ciprian Duma <[EMAIL PROTECTED]> wrote: It's in the reports section. But I think the plugin calls first pdm-check and I can't tell it not to fail (or it ignores the option). On 8/9/06, Denis Cabasson <[EMAIL PROTECTED]> wrote: > > Add the pmd plugin to your reporting section instead of your build section, > and it shouldn't breal the build anymore (but still generate the report). > > Denis. > > > Ciprian Duma wrote: > > > > How can I configure the PMD plugin not to fail the build when > > generating the report? I tried passing the parameter "failOnViolation" > > with value "false" but it's ignored. And I dont want to configure this > > plugin in the "build" section, it should be called only when is site > > is generated. > > > > The classes that fail this report were automatically generated. > > > > Thx, > > > > Ciprian > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: http://www.nabble.com/PMD-report-plugin-fails-the-build-tf2077581.html#a5722804 > Sent from the Maven - Users forum at Nabble.com. > > > - > 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMD report plugin fails the build
It's in the reports section. But I think the plugin calls first pdm-check and I can't tell it not to fail (or it ignores the option). On 8/9/06, Denis Cabasson <[EMAIL PROTECTED]> wrote: Add the pmd plugin to your reporting section instead of your build section, and it shouldn't breal the build anymore (but still generate the report). Denis. Ciprian Duma wrote: > > How can I configure the PMD plugin not to fail the build when > generating the report? I tried passing the parameter "failOnViolation" > with value "false" but it's ignored. And I dont want to configure this > plugin in the "build" section, it should be called only when is site > is generated. > > The classes that fail this report were automatically generated. > > Thx, > > Ciprian > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/PMD-report-plugin-fails-the-build-tf2077581.html#a5722804 Sent from the Maven - Users forum at Nabble.com. - 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]
Re: PMD report plugin fails the build
Add the pmd plugin to your reporting section instead of your build section, and it shouldn't breal the build anymore (but still generate the report). Denis. Ciprian Duma wrote: > > How can I configure the PMD plugin not to fail the build when > generating the report? I tried passing the parameter "failOnViolation" > with value "false" but it's ignored. And I dont want to configure this > plugin in the "build" section, it should be called only when is site > is generated. > > The classes that fail this report were automatically generated. > > Thx, > > Ciprian > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/PMD-report-plugin-fails-the-build-tf2077581.html#a5722804 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pmd report
Am 12.03.2004 um 20:47 schrieb Ryan Owens: PMD reports have been broken for a few weeks now, not PMD itself but maven's plugin:plugin I believe. Something to do with new maven plugin setting that broke old stuff or something or other. There are posts about it from a few weeks back. I think everyone is saying to just wait on PMD reports til rc2 is out. I could be wrong though, please correct me if I am. Thanks for this information! Stefan --- open technology: http://www.media-style.com open source: http://www.weta-group.net open discussion:http://www.text-mining.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pmd report
PMD reports have been broken for a few weeks now, not PMD itself but maven's plugin:plugin I believe. Something to do with new maven plugin setting that broke old stuff or something or other. There are posts about it from a few weeks back. I think everyone is saying to just wait on PMD reports til rc2 is out. I could be wrong though, please correct me if I am. cheers, Ryan On Mar 12, 2004, at 9:53 AM, [EMAIL PROTECTED] wrote: Hi, sorry i'm new to the pmd plugin. I was reading the plugin documentation and it least i understand that i only have to add the pmd plugin to my reports. I got no errors until site:generate but the report is empty. So there are 0 files analyzed. Can someone give me a hint or point me to a documentation i miss to find how to setup pmd report? Thanks! Stefan - 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]
Re: PMD Report processing 0 files.
Hello Emmanuel. I tried from the official binary release. Are any fix? thnx "Emmanuel Venisse" <[EMAIL PROTECTED]> ha scritto nel messaggio news:[EMAIL PROTECTED] > The correct branch for Maven is MAVEN-1_0-BRANCH and not HEAD > > Emmanuel > > - Original Message - > From: "kimbuba" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, February 19, 2004 12:01 PM > Subject: Re: PMD Report processing 0 files. > > > > I got the same problem, > > I tried all the instructions but nothing. > > > > Let me know if you did it. > > > > > > "Ryan Owens" <[EMAIL PROTECTED]> ha scritto nel messaggio > > news:[EMAIL PROTECTED] > > > I'm running HEAD for maven and maven-plugins. > > > PMD is currently processing 0 files, I've tried both with and without > > > custom rulesets. > > > It almost seems like PMD isn't finding any files to report on, but the > > > checkstyle report, javadoc and xref all work fine. > > > > > > These reports used to work. Am I missing a property somewhere or did > > > something else change recently that I'm missing? > > > > > > Thanks! > > > > > > > > > > - > > 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]
Re: PMD Report processing 0 files.
The correct branch for Maven is MAVEN-1_0-BRANCH and not HEAD Emmanuel - Original Message - From: "kimbuba" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 19, 2004 12:01 PM Subject: Re: PMD Report processing 0 files. > I got the same problem, > I tried all the instructions but nothing. > > Let me know if you did it. > > > "Ryan Owens" <[EMAIL PROTECTED]> ha scritto nel messaggio > news:[EMAIL PROTECTED] > > I'm running HEAD for maven and maven-plugins. > > PMD is currently processing 0 files, I've tried both with and without > > custom rulesets. > > It almost seems like PMD isn't finding any files to report on, but the > > checkstyle report, javadoc and xref all work fine. > > > > These reports used to work. Am I missing a property somewhere or did > > something else change recently that I'm missing? > > > > Thanks! > > > > > - > 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]
Re: PMD Report processing 0 files.
I got the same problem, I tried all the instructions but nothing. Let me know if you did it. "Ryan Owens" <[EMAIL PROTECTED]> ha scritto nel messaggio news:[EMAIL PROTECTED] > I'm running HEAD for maven and maven-plugins. > PMD is currently processing 0 files, I've tried both with and without > custom rulesets. > It almost seems like PMD isn't finding any files to report on, but the > checkstyle report, javadoc and xref all work fine. > > These reports used to work. Am I missing a property somewhere or did > something else change recently that I'm missing? > > Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: PMD report exclusions
Fixed and working now, thanks dIon. Nick > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 20 November 2003 14:24 > To: [EMAIL PROTECTED] > Subject: RE: PMD report exclusions > > > > Issue raised > (http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1044), > > Thanks, > > Nick > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > Sent: 20 November 2003 03:18 > > To: Maven Users List > > Subject: Re: PMD report exclusions > > > > > > 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] > > > > > > - > 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]
RE: PMD report exclusions
Issue raised (http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1044), Thanks, Nick > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 20 November 2003 03:18 > To: Maven Users List > Subject: Re: PMD report exclusions > > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMD report exclusions
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]
