Here's what I do in my parent POM file:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<dependencies>
<dependency>
<groupId>my.group</groupId>
<artifactId>build-tools</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<configuration>
<configLocation>style/my-style.xml</configLocation>
<headerLocation>style/header.java</headerLocation>
</configuration>
</plugin>
</plugins>
</reporting>
I will admit that I have not closely checked that it is actually using
the custom configuration (I have been too busy recently getting other
documentation together), but the checkstyle plugin does not complain
about missing configuration files.
HTH
-----Original Message-----
From: Robert Biernat [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 29, 2006 23:42
To: '[email protected]'
Subject: [m2] reporting plugin extensions/additional dependencies
Hi,
I'm using maven on a number of different projects. These projects all
generate websites containing reports generated by the checkstyle, pmd,
and
jdepend report plugins. The checkstyle and pmd plugins reference config
files that are tailored to my organisations coding standards. At the
moment
each project that wishes to use these standard config files needs to
include
them within their project so theyre available when the plugin runs. I am
wondering whether its possible to create a seperate project that
contains
these resources, install the jar into the repository and have the
various
report plugins use it. I noticed that for report plugins I cannot
specify
additional dependencies like I can with regular build plugins, so I'm
sort
of stuck as to how I would do it.
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
