The assumption is that you are using Maven in a large/corporate
environment for many projects, and sharing things like Checkstyle
configs etc in all of them.

Some people construct a simple Maven project, in their own company
groupId with an artifactId of say project-standards, and then bundle
things like checkstyle configs etc, and then put that dependency in
their corporate pom which is the parent for all projects in the
organization. The plugins will automatically find these config files
while building the project.

Then when anyone builds any Maven project in the organization, they
inherit things like checkstyle configs etc which helps to enforce
particular coding styles and standards, reducing bugs, etc.

Another alternative like Dário suggested is the http://... config
file. This works too and again can easily be shared across projects.
Or file:/// if you can guarantee the file will be in a specific
location on everyone's machines (keep in mind cross-platform issues if
you have multiple architectures in your environment).

Finally, the last (and least desirable, for me at least) option is to
put the checkstyle config directly inside your project. I've never
done this but it would probably be found if you put it under
src/main/resources.

Wayne

On 1/23/07, Dário Luís Coneglian Oliveros <[EMAIL PROTECTED]> wrote:
Hi Jeff,
Not really. You can either create an artifact that contains your checkstyle 
config file and add it to your project as a dependency or you could specify its 
URL.
Personally I would recommend the second one. Here's a snippet of my pom.xml.
             ...
               <configuration>
                   
<configLocation>http://your.domain.goes.here/jeff_checks.xml</configLocation>
               </configuration>
             ...
You could also use file:// if you want to.
Dário

-----Original Message-----
From: Jeff Mutonho [mailto:[EMAIL PROTECTED]
Sent: terça-feira, 23 de janeiro de 2007 05:32
To: Maven Users List
Subject: Re: Out of memory error


On 1/22/07, Dário Luís Coneglian Oliveros <[EMAIL PROTECTED]> wrote:
> I've faced the same problem.
> It seems to be a bug in the checkstyle plugin.
> I've noticed it happens only if there are too many checkstyle errors.
> My suggestion is to decrease this number to about 10000 (hopefully most of 
them are tab related).
> It should work. Do not ask me why :-)
> Dário
>

I'm looking at the maven-checkstyle-plugin in my pom and it says ,
<configLocation>config/sun_checks.xml</configLocation>

I understand  that sun_checks.xml is located in the config directory ,
in the plugin jar.If I wish to specify my own as :
<configLocation>jeffs-checks.xml</configLocation>


The plugin documentation says that when one specifies a custom
check-style file as above  it
"causes the Maven 2 Checkstyle plugin to check for a File named
checkstyle.xml or a resource named checkstyle.xml within the compile
scope of the dependencies or build extensions classpath."

From this , does that mean  "jeffs-checks.xml" above should be located
in the same directory as the pom.xml?

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042

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