[maven-scm-plugin] prepare release 1.7.1

git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@263839 13f79535-47bb-0310-9956-ffa450edef68

ejb/xdocs/changes.xml

@@ -23,11 +23,8 @@
     <author email="nathan.coast@blueyonder.co.uk">Nathan Coast</author>
   </properties>
   <body>
-    <release version="1.7.1" date="in SVN">
-      <action dev="brett" type="fix">
-        Update dependency to Maven Model v3.0.0 final (it was previously depending
-        on 3.0.0 SNAPSHOT).
-      </action>
+    <release version="1.7.1" date="2005-08-28">
+      <action dev="brett" type="fix">Update dependency to Maven Model v3.0.0 final (it was previously depending on 3.0.0 SNAPSHOT).</action>
     </release>
     <release version="1.7" date="2005-08-27">
       <action dev="vmassol" type="update">By default do not generate client EJB. I believe this is a more common default that generating as generation of client EJBs is only required for distributed apps which are not so common.</action>
@@ -40,7 +37,7 @@
         <code>ejb:deploy</code>). Previous goals dedicated to ejb client have been deprecated. There is a new property
         <code>maven.ejb.client.generate</code>which decides whether or not to generate the ejb client jar. It defaults to true.
       </action>
-      <action dev="vmassol" type="fix" issue="MPEJB-16" due-to="H�vard Bj�stad">Added new EJB type handler that supports
+      <action dev="vmassol" type="fix" issue="MPEJB-16" due-to="H�vard Bj�stad">Added new EJB type handler that supports
         <code>ejb</code>and
         <code>ejb-client</code>types. This fixes the bug with
         <code>ejb:install/deploy-client</code>not uploading the client jar.