I've put pmd config into <build> section of my pom (exactly as is in documentation). Still no effect and empty pmd.xml:
<?xml version="1.0" encoding="UTF-8"?> <pmd version="4.3" timestamp="2012-02-07T08:34:59.070"> </pmd> Please advise 2012/2/7 Barrie Treloar <baerr...@gmail.com> > On Tue, Feb 7, 2012 at 7:19 AM, Wayne Fay <wayne...@gmail.com> wrote: > >> Jenkins CI. I don't need full site lifecycle. The reason why pmd is > needed > >> -- is to enforce coding style and standarts and fail build in case of > some > >> violations. There is no need of html/csv reports in my scenario at all. > > > > I don't use this plugin as a regular thing so I can't tell you why it > > isn't working. I am simply going on the documentation that is > > published. > > > > If you aren't using the site and just want to have PMD complain about > > rule violations, you probably don't want to use the <reporting> > > section but instead the <build> section of your pom. And you probably > > want to use the "check" goal. > > As Wayne says: > > http://maven.apache.org/plugins/maven-pmd-plugin/examples/violationChecking.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
