"the tip of using a dependency containing build tools doesn't work at
all"

I beg to differ.  At least the 2.0-beta-2 snapshot I have (dated
20051230.164525-2) has this working just fine.  The POM has to be
arranged:
<project>
    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-checkstyle-plugin</artifactId>
                <version>2.0-beta-2-SNAPSHOT</version>
                <dependencies>
                    <dependency>
                        <groupId>this.is.a.group</groupId>
                        <artifactId>build-tools</artifactId>
                        <version>3.0-SNAPSHOT</version>
                    </dependency>
                </dependencies>
            </plugin>
        </plugins>
    </build>
    <reporting>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-checkstyle-plugin</artifactId>
                <version>2.0-beta-2-SNAPSHOT</version>
                <configuration>
                    <configLocation>style/Q.Access.xml</configLocation>
                    <headerLocation>style/header.java</headerLocation>
                </configuration>
            </plugin>
        </plugins>
    </reporting>
</project>

With this POM (of course, I left a bunch of other stuff out like that
the build-tools artifact is a module of this POM), CheckStyle pulls the
configuration and header out of the build-tools jar file.  And this
works on all of the modules of this POM without a hitch.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fabrizio
Giustina
Sent: Monday, January 23, 2006 2:37 PM
To: Maven Developers List
Subject: Re: [vote] Release maven 2 checkstyle plugin

On 1/23/06, Brett Porter <[EMAIL PROTECTED]> wrote:
> Should it be final or beta? How certain is it that future changes will

> be backwards compatible, and how serious are the bugs?

It works fine and (AFAIK) there are no planned breaking changes. The
only important issue open is how to share configuration files in a
multi-project build: actually that can easily be done by using a shared
file with relative paths or an url, but the tip of using a dependency
containing build tools doesn't work at all and can't be used for reports
(the plugin element in the reporting section of pom doesn't support
per-plugin dependencies). Did you see the recent commit mails about that
topic?
Anyway, that issue is generic to any plugin that have to share a
configuration file in a multi-module build; the checkstyle plugin now
works fine and important classloader issues have been fixed so it surely
deserves a non-beta release.

fabrizio

---------------------------------------------------------------------
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to