Except that the build-tools jar should be referred to as an extension,
not a dependency of the plugin. My experience was that Maven would
only try ibiblio to look for the build-tools jar if I left it as a
plugin dependency.
See the bottom of this checkstyle plugin doc for an example:
http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html
-Stephen
On 7/24/06, dcabasson <[EMAIL PROTECTED]> wrote:
Nick Panienski wrote:
>
> As far as I know I cannot include XMLs in a project that has a
> <packaging>pom</packaging>. I already tried to build a resources project
> packaged as a jar and define a dependency in my parent pom. Maven doesn't
> complain about this, but I still don't know how to access my config
> files...
>
Common practice is indeed to have a build-tools module, with packaging jar.
To use this module (with checkstyle), in the build/plugins part, of your
parent POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<dependencies>
<dependency>
<groupId>com.myApplication</groupId>
<artifactId>build-tools</artifactId>
<version>1.2-SNAPSHOT</version>
</dependency>
</dependencies>
<configuration>
<configLocation>your_checks.xml</configLocation>
</configuration>
</plugin>
Every sub-project will now use this checkstyle configuration.
Denis.
--
View this message in context:
http://www.nabble.com/Parent-POM-with-Resources-tf1990950.html#a5463782
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
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]
