2004-01-29 05:34:55 +00:00

81 lines
2.7 KiB
XML

<?xml version="1.0"?>
<document>
<properties>
<title>Checkstyle plugin changes</title>
<author email="vmassol@octo.com">Vincent Massol</author>
<author email="evenisse@ifrance.com">Emmanuel Venisse</author>
</properties>
<body>
<release version="2.3" date="in CVS">
<action dev="dion" type="update">
Applied MPCHECKSTYLE-15
</action>
<action dev="vmassol" type="update">
Upgraded to Checkstyle 3.3.
</action>
</release>
<release version="2.2" date="2003-12-22">
<action dev="vmassol" type="fix" issue="MPCHECKSTYLE-2" due-to="Henri Tremblay">
The Checkstyle HTML report now provides information on severity.
</action>
<action dev="vmassol" type="fix">
Prevent projects who do not use the head check from failing if they
don't provide a license file.
</action>
<action dev="vmassol" type="update">
Upgraded to Checkstyle 3.2.
</action>
</release>
<release version="2.1" date="Unknown">
</release>
<release version="2.0" date="2003-09-01">
<action dev="dion" type="fix" issue="MPCHECKSTYLE-3">
Added ignoreLines 1, 6.
</action>
<action dev="dion" type="update">
Update to use maven.docs.*/maven.gen.docs
</action>
<action dev="dion" type="fix">
Add maven dependency and classes directory to classpath. This stops
'Unable to get class information for '&lt;classname&gt;' errors.
</action>
<action dev="evenisse" type="fix">
Add xml declaration to generated report. Fixed for character encoding.
</action>
<action dev="evenisse" type="fix" issue="MPCHANGELOG-9">
I register reports only if source, test,... exists.
So, corresponding entrys in menu will appear only if reports are
registered.
</action>
<action dev="evenisse" type="fix" issue="MPCHECKSTYLE-1">
</action>
<action dev="vmassol" type="update">
Upgraded to Checkstyle 3.1.
</action>
<action dev="vmassol" type="update">
Updated documentation.
</action>
<action dev="vmassol" type="update">
Complete clean of the existing plugin.
</action>
</release>
<release version="1.1" date="2003-05-30">
<action dev="vmassol" type="add">
Added a new <code>maven.checkstyle.useFile</code> property.
If false, the checkstyle task will display violations on stdout.
If true, a text file will be created with the violations. Note:
this is in addition to the XML result file (containing the
violations in XML format) which is always created.
</action>
</release>
</body>
</document>