Solved it. The problem was I didn't include the <configLocation> tag in the 
<build> section. It was only included in the <reporting> section. Somehow, this 
used to work in 2.2.1. I guess Maven 3.0 is tighter in this regard ;-).

> -----Original Message-----
> From: Thiessen, Todd (Todd) [mailto:tthies...@avaya.com]
> Sent: Monday, October 18, 2010 8:05 AM
> To: Maven Users List
> Subject: RE: Maven 3.0 and checkstyle plugin
> 
> Thanks Dennis. Its from the build section. More specifically,
> pluginmanagement.
> 
> Thanks also for those links. I took a look at the compatibility matrix
> and for checkstyle there is this jira:
> 
> http://jira.codehaus.org/browse/MCHECKSTYLE-123
> 
> Although it says it has been fixed as of 2.5. But the last comment from
> Oliver states:
> 
> "Leave it open as some its continue to failed with mvn 3.x"
> 
> So I am not entirely sure if this means there is still a problem or if it
> has been fixed ;-).
> 
> > -----Original Message-----
> > From: Dennis Lundberg [mailto:denn...@apache.org]
> > Sent: Saturday, October 16, 2010 10:07 AM
> > To: Maven Users List
> > Subject: Re: Maven 3.0 and checkstyle plugin
> >
> > My guess is that your configuration is in the wrong place. Have you
> read
> > the "Maven 3 Compatibility Notes" and "Maven 3 and Site Plugin"?
> >
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility
> > +Notes
> >
> >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plug
> > in
> >
> > Is the snippet below from the <build> or from the <reporting> section
> of
> > your POM?
> >
> > On 2010-10-15 23:52, Thiessen, Todd (Todd) wrote:
> > > Is anyone else having trouble with the maven-checkstyle-plugin with
> > maven 3.0? Specifically with using a custom rule set. The following
> > snippet would find our custom rules in 2.2.1 but does not in 3.0.
> > >
> > >         <plugin>
> > >           <groupId>org.apache.maven.plugins</groupId>
> > >           <artifactId>maven-checkstyle-plugin</artifactId>
> > >           <version>2.6</version>
> > >           <configuration>
> > >              <violationSeverity>warning</violationSeverity>
> > >              <consoleOutput>true</consoleOutput>
> > >           </configuration>
> > >           <executions>
> > >              <execution>
> > >                 <id>checkstyle-main</id>
> > >                 <phase>verify</phase>
> > >                 <goals><goal>check</goal></goals>
> > >              </execution>
> > >           </executions>
> > >           <dependencies>
> > >             <dependency>
> > >               <groupId>groupid.of.rules</groupId>
> > >               <artifactId>artifactid.of.rules</artifactId>
> > >               <version>version.of.rules</version>
> > >             </dependency>
> > >           </dependencies>
> > >         </plugin>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: users-h...@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Dennis Lundberg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to