[ http://jira.codehaus.org/browse/MPMD-22?page=comments#action_61838 ]
Carlos Sanchez commented on MPMD-22: ------------------------------------ It worked since 2.0 http://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html <build> <plugins> <plugin> <groupId/> <artifactId/> <version/> <dependencies> <dependency> <groupId/> <artifactId/> <version/> </dependency> </dependencies> </plugin> </plugins> </build> > PMD plugin <configuration> should accept dependency entries > ----------------------------------------------------------- > > Key: MPMD-22 > URL: http://jira.codehaus.org/browse/MPMD-22 > Project: Maven 2.x Pmd Plugin > Type: New Feature > Reporter: Subhash Chandran > > > As described here: > http://maven.apache.org/plugins/maven-pmd-plugin/howto.html > The PMD plugin supports configuration of custom ruleset XML files. But in our > organization, we have written custom ruleset XMLs that refer Java classes > (our PMD extension dependencies). The configuration of the PMD plugin should > allow these dependencies to be specified. > Since we do not have this feature in the current release, we at our > organization are forced to maintain a fork of the PMD plugin with the > necessary dependencies added. > A suggested format: > <configuration> > <rulesets> > <ruleset>/rulesets/basic.xml</ruleset> > <ruleset>/rulesets/controversial.xml</ruleset> > <ruleset>d:\rulesets\strings.xml</ruleset> > <ruleset>http://localhost/design.xml</ruleset> > </rulesets> > {color:red} > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <version>4.0</version> > <scope>test</scope> > </dependency> > {color} > <format>xml</format> > <linkXref>true</linkXref> > <sourceEncoding>utf-8</sourceEncoding> > <minimumTokens>100</minimumTokens> > </configuration> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
