[maven-scm-plugin] prepare release 1.5

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@356475 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
ltheussl committed 2005-12-13 05:25:03 +00:00
1 parent 46eb0494ba
commit 4dff7c0430
2 files changed
+37 -47

No files matched your search

+30 -43
View File
@@ -1,4 +1,5 @@
<?xml version="1.0"?>
<?xml version="1.0" encoding="UTF-8"?>
<!--
/*
* Copyright 2001-2005 The Apache Software Foundation.
@@ -16,55 +17,41 @@
* limitations under the License.
*/
-->
<document>
<properties>
<title>Changes</title>
<author email="dion@apache.org">dIon Gillard</author>
</properties>
<body>
<release version="1.5-SNAPSHOT" date="in SVN">
<action dev="ltheussl" type="fix" issue="MPPOM-1"><code>pom:validate</code> doesn't work with <code>&lt;extend&gt;</code>.</action>
<action dev="ltheussl" type="fix" issue="MPPOM-5"><code>pom:validate</code> doesn't work.</action>
<action dev="aheritier" type="update" issue="MAVEN-1712">Update dependencies to match ones in maven 1.1 core and to unify them between plugins. The following dependencies are updated :
<release version="1.5" date="2005-12-12">
<action dev="ltheussl" type="fix" issue="MPPOM-1">
<code>pom:validate</code>doesn't work with
<code>&lt;extend&gt;</code>.
</action>
<action dev="ltheussl" type="fix" issue="MPPOM-5">
<code>pom:validate</code>doesn't work.
</action>
<action dev="aheritier" type="update" issue="MAVEN-1712">Update dependencies to match ones in maven 1.1 core and to unify them between plugins. The following dependencies are updated :
<ul>
<li>dom4j v1.4-dev-8 -> v1.4</li>
<li>maven v1.0 -> v1.0.2</li>
<li>dom4j v1.4-dev-8 -&gt; v1.4</li>
<li>maven v1.0 -&gt; v1.0.2</li>
</ul>
</action>
</release>
<release version="1.4.1" date="2004-06-19">
<action dev="brett" type="fix">Build and run plugin against the installed version of Maven</action>
</release>
<release version="1.4" date="unknown">
<action dev="brett" type="remove" issue="MPPOM-2">
remove empty pom:update goal
</action>
<action dev="evenisse" type="add">
Add missing xml-apis jar.
</action>
<action dev="vmassol" type="add">
Verify valid POM versions. Only "3" and "4" are currently allowed.
</action>
<action dev="vmassol" type="add">
Added support for validating different POM versions.
</action>
</release>
<release version="1.3" date="2003-09-29">
<action dev="dion" type="fix">
Make pom:validate work again. The xerces upgrade broke jarv.
Now using jing
</action>
<action dev="dion" type="update">
Upgrade to maven 1.0 beta 10 and dom4j 1.4
</action>
<action dev="dion" type="update">
Upgrade to dom4j 1.4-dev-8
</action>
<action dev="dion" type="fix">
Bring back pom:validate
</action>
</release>
</body>
</release>
<release version="1.4.1" date="2004-06-19">
<action dev="brett" type="fix">Build and run plugin against the installed version of Maven</action>
</release>
<release version="1.4" date="unknown">
<action dev="brett" type="remove" issue="MPPOM-2">remove empty pom:update goal</action>
<action dev="evenisse" type="add">Add missing xml-apis jar.</action>
<action dev="vmassol" type="add">Verify valid POM versions. Only "3" and "4" are currently allowed.</action>
<action dev="vmassol" type="add">Added support for validating different POM versions.</action>
</release>
<release version="1.3" date="2003-09-29">
<action dev="dion" type="fix">Make pom:validate work again. The xerces upgrade broke jarv. Now using jing</action>
<action dev="dion" type="update">Upgrade to maven 1.0 beta 10 and dom4j 1.4</action>
<action dev="dion" type="update">Upgrade to dom4j 1.4-dev-8</action>
<action dev="dion" type="fix">Bring back pom:validate</action>
</release>
</body>
</document>