You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by vm...@apache.org on 2005/08/27 16:17:43 UTC

svn commit: r240421 - in /maven/maven-1/plugins/trunk/ejb: project.xml xdocs/changes.xml

Author: vmassol
Date: Sat Aug 27 07:17:36 2005
New Revision: 240421

URL: http://svn.apache.org/viewcvs?rev=240421&view=rev
Log:
[maven-scm-plugin] prepare release 1.7

Modified:
    maven/maven-1/plugins/trunk/ejb/project.xml
    maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml

Modified: maven/maven-1/plugins/trunk/ejb/project.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/project.xml?rev=240421&r1=240420&r2=240421&view=diff
==============================================================================
--- maven/maven-1/plugins/trunk/ejb/project.xml (original)
+++ maven/maven-1/plugins/trunk/ejb/project.xml Sat Aug 27 07:17:36 2005
@@ -17,13 +17,12 @@
  * limitations under the License.
  */
  -->
-
 <project>
   <extend>../plugin-parent/project.xml</extend>
   <pomVersion>3</pomVersion>
   <id>maven-ejb-plugin</id>
   <name>Maven EJB Plugin</name>
-  <currentVersion>1.7-SNAPSHOT</currentVersion>
+  <currentVersion>1.7</currentVersion>
   <description>EJB Plugin for Maven</description>
   <shortDescription>EJB Plugin for Maven</shortDescription>
   <url>http://maven.apache.org/reference/plugins/ejb/</url>
@@ -55,6 +54,11 @@
       <name>1.6</name>
       <tag>MAVEN_EJB_1_6</tag>
     </version>
+    <version>
+      <id>1.7</id>
+      <name>1.7</name>
+      <tag>MAVEN_EJB_1_7</tag>
+    </version>
   </versions>
   <mailingLists/>
   <developers>
@@ -85,7 +89,7 @@
   </developers>
   <contributors>
     <contributor>
-      <name>Håvard Bjåstad</name>
+      <name>Håvard Bjåstad</name>
     </contributor>
   </contributors>
   <dependencies>

Modified: maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml?rev=240421&r1=240420&r2=240421&view=diff
==============================================================================
--- maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml Sat Aug 27 07:17:36 2005
@@ -17,59 +17,41 @@
  * limitations under the License.
  */
  -->
-
 <document>
   <properties>
     <title>Changes</title>
     <author email="nathan.coast@blueyonder.co.uk">Nathan Coast</author>
   </properties>
   <body>
-    <release version="1.7-SNAPSHOT" date="in SVN trunk">
-      <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>
-      <action dev="vmassol" type="fix">
-        Make the ejb creation work even if there are not sources. 
-      </action>
-      <action dev="vmassol" type="fix" issue="MPEJB-12">
-        Fixed default property values in the web site documentation.
-      </action>
-      <action dev="vmassol" type="fix" issue="MPEJB-2">
-        EJB client jar can now be generated and deployed/installed
-        automatically by the standard goals (<code>ejb</code>, <code>ejb:ejb</code>,
-        <code>ejb:install</code> and <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 <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.
+    <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>
+      <action dev="vmassol" type="fix">Make the ejb creation work even if there are not sources.</action>
+      <action dev="vmassol" type="fix" issue="MPEJB-12">Fixed default property values in the web site documentation.</action>
+      <action dev="vmassol" type="fix" issue="MPEJB-2">EJB client jar can now be generated and deployed/installed automatically by the standard goals (
+        <code>ejb</code>,
+        <code>ejb:ejb</code>,
+        <code>ejb:install</code>and
+        <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
+        <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.
       </action>
     </release>
     <release version="1.6" date="2005-05-01">
-      <action dev="vmassol" type="add">
-        Added new <code>maven.ejb.build.dir</code> property that specifies the
-        location where the EJBs are generated.
-      </action>
-      <action dev="vmassol" type="update">
-        Modified existing <code>maven.ejb.final.name</code> property (and 
-        exposed it as a public property) so that it doesn't include the path 
-        (the path is now provided by the new <code>maven.ejb.build.dir</code> 
-        property). This allows aligning the WAR and EJB plugin properties. 
-        Note: This is a breaking change for all those using the 
-        <code>maven.ejb.final.name</code> property (which was not a public 
-        property).
+      <action dev="vmassol" type="add">Added new
+        <code>maven.ejb.build.dir</code>property that specifies the location where the EJBs are generated.
       </action>
-      <action dev="vmassol" type="update">
-        Made the <code>maven.ejb.final.name</code> property public as it is 
-        required by several other plugins and before this change the only 
-        way is for these plugins was to call the non-public 
-        <code>ejb:init</code> goal.
+      <action dev="vmassol" type="update">Modified existing
+        <code>maven.ejb.final.name</code>property (and exposed it as a public property) so that it doesn't include the path (the path is now provided by the new
+        <code>maven.ejb.build.dir</code>property). This allows aligning the WAR and EJB plugin properties. Note: This is a breaking change for all those using the
+        <code>maven.ejb.final.name</code>property (which was not a public property).
+      </action>
+      <action dev="vmassol" type="update">Made the
+        <code>maven.ejb.final.name</code>property public as it is required by several other plugins and before this change the only way is for these plugins was to call the non-public
+        <code>ejb:init</code>goal.
       </action>
     </release>
     <release version="1.5" date="2004-07-09">



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org