Bommels05/maven-plugins
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[maven-scm-plugin] prepare release 2.3

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@114897 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
brett 2004-03-10 14:00:07 +00:00
parent 55d9aa1ebb
commit ce52ef4499
2 changed files with 27 additions and 65 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
checkstyle/project.xml
View File

@ -1,4 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!-- <!--
/* /*
* Copyright 2001-2004 The Apache Software Foundation. * Copyright 2001-2004 The Apache Software Foundation.
@ -17,13 +18,12 @@
*/ */
--> -->
<project> <project>
<extend>../project.xml</extend> <extend>../project.xml</extend>
<pomVersion>3</pomVersion> <pomVersion>3</pomVersion>
<id>maven-checkstyle-plugin</id> <id>maven-checkstyle-plugin</id>
<name>Maven Checkstyle Plug-in</name> <name>Maven Checkstyle Plug-in</name>
<currentVersion>2.3-SNAPSHOT</currentVersion> <currentVersion>2.3</currentVersion>
<description/> <description/>
<shortDescription>Produce Checkstyle report</shortDescription> <shortDescription>Produce Checkstyle report</shortDescription>
<url>http://maven.apache.org/reference/plugins/checkstyle/</url> <url>http://maven.apache.org/reference/plugins/checkstyle/</url>
@ -55,6 +55,11 @@
<name>2.3</name> <name>2.3</name>
<tag>HEAD</tag> <tag>HEAD</tag>
</version> </version>
<version>
<id>2.3</id>
<name>2.3</name>
<tag>MAVEN_CHECKSTYLE_2_3</tag>
</version>
</versions> </versions>
<developers> <developers>
<developer> <developer>

83
checkstyle/xdocs/changes.xml
View File

@ -1,4 +1,5 @@
<?xml version="1.0"?> <?xml version="1.0" encoding="UTF-8"?>
<!-- <!--
/* /*
* Copyright 2001-2004 The Apache Software Foundation. * Copyright 2001-2004 The Apache Software Foundation.
@ -23,76 +24,32 @@
<author email="vmassol@octo.com">Vincent Massol</author> <author email="vmassol@octo.com">Vincent Massol</author>
<author email="evenisse@ifrance.com">Emmanuel Venisse</author> <author email="evenisse@ifrance.com">Emmanuel Venisse</author>
</properties> </properties>
<body> <body>
<release version="2.3" date="2004-03-11">
<release version="2.3" date="in CVS"> <action dev="dion" type="update">Applied MPCHECKSTYLE-15</action>
<action dev="dion" type="update"> <action dev="vmassol" type="update">Upgraded to Checkstyle 3.3.</action>
Applied MPCHECKSTYLE-15
</action>
<action dev="vmassol" type="update">
Upgraded to Checkstyle 3.3.
</action>
</release> </release>
<release version="2.2" date="2003-12-22"> <release version="2.2" date="2003-12-22">
<action dev="vmassol" type="fix" issue="MPCHECKSTYLE-2" due-to="Henri Tremblay"> <action dev="vmassol" type="fix" issue="MPCHECKSTYLE-2" due-to="Henri Tremblay">The Checkstyle HTML report now provides information on severity.</action>
The Checkstyle HTML report now provides information on severity. <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> <action dev="vmassol" type="update">Upgraded to Checkstyle 3.2.</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>
<release version="2.1" date="Unknown"></release>
<release version="2.1" date="Unknown">
</release>
<release version="2.0" date="2003-09-01"> <release version="2.0" date="2003-09-01">
<action dev="dion" type="fix" issue="MPCHECKSTYLE-3"> <action dev="dion" type="fix" issue="MPCHECKSTYLE-3">Added ignoreLines 1, 6.</action>
Added ignoreLines 1, 6. <action dev="dion" type="update">Update to use maven.docs.*/maven.gen.docs</action>
</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="dion" type="update"> <action dev="evenisse" type="fix">Add xml declaration to generated report. Fixed for character encoding.</action>
Update to use maven.docs.*/maven.gen.docs <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> <action dev="evenisse" type="fix" issue="MPCHECKSTYLE-1"></action>
<action dev="dion" type="fix"> <action dev="vmassol" type="update">Upgraded to Checkstyle 3.1.</action>
Add maven dependency and classes directory to classpath. This stops <action dev="vmassol" type="update">Updated documentation.</action>
'Unable to get class information for '&lt;classname&gt;' errors. <action dev="vmassol" type="update">Complete clean of the existing plugin.</action>
</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>
<release version="1.1" date="2003-05-30"> <release version="1.1" date="2003-05-30">
<action dev="vmassol" type="add"> <action dev="vmassol" type="add">Added a new
Added a new <code>maven.checkstyle.useFile</code> property. <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.
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> </action>
</release> </release>
</body> </body>
</document> </document>