Hi Tim,
I recently did something like this (with PMD instead). I used
<extensions> then someone suggested I not use it -- it seems
<extensions> is headed towards deprecation. Instead under
build/plugins/plugin add you stuff as a dependency. Something like this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId> <!- I'm
guessing at the name ->
<dependencies>
<dependency>
<groupId>com.xxx</groupId>
<artifactId>xxxx-checkstyle</artifactId>
<version>1.0.o</version>
</dependency>
</dependencies>
</plugin>
Regards,
Chris
-----Original Message-----
From: Tim Foster [mailto:[EMAIL PROTECTED]
Sent: Friday, May 18, 2007 11:51 AM
To: Maven Users List
Subject: RE: How to share a common checkstyle config across modules?
Thanks, Gerald. This is exactly what I wanted and it worked just as you
described. This mechanism will be useful for many other applications.
Tim
-----Original Message-----
From: Nunn, Gerald [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 17, 2007 1:52 PM
To: Maven Users List
Subject: RE: How to share a common checkstyle config across modules?
I jar my checkstyle configuration and then store it in an intranet Maven
repository. Projects can then declare a dependency on this jar using the
extensions tag in the build section of pom.xml. For example:
<build>
<extensions>
<extension>
<groupId>com.xxxx</groupId>
<artifactId>xxxx-checkstyle</artifactId>
<version>1.0.0</version>
</extension>
</extensions>
</build>
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<configuration>
<configLocation>config/cibc_checks.xml</configLocation>
</configuration>
</plugin>
</plugins>
</reporting>
The configLocation is the classpath location in the xxxx-checkstyle.jar.
Hope this helps.
Gerald
---------------------------------------------------------------------
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]
**********************************************************************
This communication and all information (including, but not limited to,
market prices/levels and data) contained therein (the "Information") is
for informational purposes only, is confidential, may be legally
privileged and is the intellectual property of ICAP plc and its affiliates
("ICAP") or third parties. No confidentiality or privilege is waived or
lost by any mistransmission. The Information is not, and should not
be construed as, an offer, bid or solicitation in relation to any
financial instrument or as an official confirmation of any transaction.
The Information is not warranted, including, but not limited, as to
completeness, timeliness or accuracy and is subject to change
without notice. ICAP assumes no liability for use or misuse of the
Information. All representations and warranties are expressly
disclaimed. The Information does not necessarily reflect the views of
ICAP. Access to the Information by anyone else other than the
recipient is unauthorized and any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it is prohibited. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and
notify the sender.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
