Just been doing this myself and you can use regular plugin
dependencies rather than resorting to extensions.  For example,
putting this in your company-wide parent pom will run checkstyle:check
at the verify phase:

        <build>
                <plugins>
                        <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-checkstyle-plugin</artifactId>
                                <configuration>
                                        
<configLocation>checkstyle.xml</configLocation>
                                </configuration>
                                <executions>
                                        <execution>
                                                <goals>
                                                        <goal>check</goal>
                                                </goals>
                                        </execution>
                                </executions>
                                <dependencies>
                                        <dependency>
                                                <groupId>mygroup</groupId>
                                                <artifactId>mybuild</artifactId>
                                                <version>1.0</version>
                                        </dependency>
                                </dependencies>
                        </plugin>
                </plugins>
        </build>

This assumes an artifact mygroup:mybuild:jar:1.0 that contains your
shared checkstyle.xml.

Mark

On 04/12/06, Trevor Torrez <[EMAIL PROTECTED]> wrote:
Yup; i agree; versioning everything associated with the build is a good
idea, and currently we do do this; I was hoping to get rid of the
duplications from project to project in an elegent manner; c'est la vie.

The maven-remote-resources plugin, although it would work, doesn't seem
right either.  After all, I dont want to package the checkstyles.xml file
with anything, it doesnt really get distributed; so thats a no.


On 12/4/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
>
> On 12/4/06, Trevor Torrez <[EMAIL PROTECTED]> wrote:
>
> > Thanks; I had thought about that, I was hoping there was something
> simpler
> > and just as transparent.  It kinda grates me to create a maven project
> and
> > repository jar file for one file; using a simple URL is tempting, but
> > anywhere we can stick the file we can stick the jar, and the simple URL
> idea
> > doesnt let us control changes to it;
>
> Yep... this is one of those times when Maven is (not so) gently
> encouraging you to do the right thing, (version everything associated
> with your build) even if it seems a bit over the top to have to
> release a jar containing a single file. :)
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> 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