You could use a parent pom file that defines the Checkstyle settings globally. Deploy the parent pom to your internal repository. In your modules use the parent pom file (do not use the relativePath element (or whatever the name is)) since you have deployed it to your internal server, it is not needed.
That configuration would avoid the need to define the Checkstyle usage and configuration in every single module. Andreas -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Saturday, September 30, 2006 4:55 PM To: Maven Users List Subject: Re: Checkstyle Behind A Firewall On 9/30/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > You could put the config file into a jar project, and depend on that > project as a build extension, and use a relative url to that file. That's how I set it up originally for Struts, but then I realized we would have to release this jar, just like we have to release the master pom, in advance of a release of the framework. The only other option I can think of is configuring the Checkstyle plugin in every single module with the correct relative path. -- 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]
