Checkstyle plugin 2.4+ uses Checkstyle 5, which has a slightly altered
configuration format. If you upgrade to 2.4+ you also need to change the
Checkstyle configuration file. Let me know if you need details, and I'll
dig them up for you.

On 2010-10-13 22:13, Niall Pemberton wrote:
> Would be better to upgrade to the more recent checkstyle plugin (2.6)
> - see details in the commit log:
> 
> http://svn.apache.org/viewvc?view=revision&revision=1005273
> 
> Niall
> 
> On Wed, Oct 13, 2010 at 9:06 PM,  <[email protected]> wrote:
>> Author: ggregory
>> Date: Wed Oct 13 20:06:41 2010
>> New Revision: 1022277
>>
>> URL: http://svn.apache.org/viewvc?rev=1022277&view=rev
>> Log:
>> maven-checkstyle-plugin 2.1 -> 2.3 (2.4 fails with "Embedded error: Error 
>> rendering Maven report: Failed during checkstyle configuration TreeWalker is 
>> not allowed as a parent of Header")
>>
>> Modified:
>>    commons/proper/pool/trunk/pom.xml
>>
>> Modified: commons/proper/pool/trunk/pom.xml
>> URL: 
>> http://svn.apache.org/viewvc/commons/proper/pool/trunk/pom.xml?rev=1022277&r1=1022276&r2=1022277&view=diff
>> ==============================================================================
>> --- commons/proper/pool/trunk/pom.xml (original)
>> +++ commons/proper/pool/trunk/pom.xml Wed Oct 13 20:06:41 2010
>> @@ -246,7 +246,7 @@
>>         <plugin>
>>           <groupId>org.apache.maven.plugins</groupId>
>>           <artifactId>maven-checkstyle-plugin</artifactId>
>> -          <version>2.1</version>
>> +          <version>2.3</version>
>>           <configuration>
>>             <configLocation>${basedir}/checkstyle.xml</configLocation>
>>             <enableRulesSummary>false</enableRulesSummary>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 
> 


-- 
Dennis Lundberg

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to