Thanks for the reply Wendy. <dependencies>...</dependencies> seems to only exist as a <plugin> subelement for <build>, not in <reporting>. Both <dependencies>...</dependencies> and <dependency>...</dependency> yield "unrecognized tag" errors for parsing in the <reporting> section.
Interestingly, Eclipse autocompletion is happy to put a <dependency> element after <configuration>! > -----Original Message----- > From: Wendy Smoak [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 06, 2008 11:15 AM > To: Maven Users List > Subject: Re: [m2] PMD plugin and custom rulesets > > On Jan 6, 2008 10:06 AM, Jeff Jensen <[EMAIL PROTECTED]> > wrote: > > I have a jar for custom PMD rules; it has Java classes and the XML rulesets. > > The rulesets are in a top-level "/rulesets" dir. > > > > I have the jar as a POM dependency: > > <dependency> > > <groupId>pmd</groupId> > > <artifactId>pmdcustomrules</artifactId> > > <version>1.2</version> > > </dependency> > > Try putting the dependency inside the pmd <plugin> element instead of > listing it as a project dependency (which it isn't.) > > -- > Wendy > http://maven.apache.org/ref/2.0.8/maven-model/maven.html > > --------------------------------------------------------------------- > 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]