You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by lt...@apache.org on 2006/02/16 19:58:03 UTC

svn commit: r378339 - in /maven/maven-1/core/trunk/xdocs: reference/backwards-compatibility.xml roadmap.xml

Author: ltheussl
Date: Thu Feb 16 10:57:59 2006
New Revision: 378339

URL: http://svn.apache.org/viewcvs?rev=378339&view=rev
Log:
Update roadmap, add more deprecated plugins in the compatibility page

Modified:
    maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml
    maven/maven-1/core/trunk/xdocs/roadmap.xml

Modified: maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml?rev=378339&r1=378338&r2=378339&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml (original)
+++ maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml Thu Feb 16 10:57:59 2006
@@ -31,7 +31,7 @@
         might encounter upgrading between Maven versions, and how to update your
         project.
       </p>
-      <subsection name="Changes Between Maven 1.0 and Maven 1.1-beta-2">
+      <subsection name="Changes Between Maven 1.0 and Maven 1.1-beta-3">
         <p>
           <b>JDK requirement is now 1.4 and above</b>
         </p>
@@ -49,19 +49,28 @@
           them to another project it will be considered.
         </p>
         <ul>
+          <li>abbot</li>
           <li>appserver</li>
           <li>ashkelon</li>
           <li>aspectwerkz</li>
           <li>caller</li>
+          <li>castor</li>
           <li>docbook <i>(note that there is a superior docbook plugin at <a href="http://maven-plugins.sf.net">the SourceForge Maven Plugins project</a>)</i></li>
+          <li>hibernate</li>
+          <li>jboss  <i>(can be replaced by <a href="http://cargo.codehaus.org/Maven1+plugin">Cargo</a>)</i></li>
+          <li>jbuilder</li>
+          <li>jcoverage</li>
           <li>jdee</li>
           <li>jdeveloper</li>
+          <li>jetty  <i>(can be replaced by <a href="http://cargo.codehaus.org/Maven1+plugin">Cargo</a>)</i></li>
+          <li>jnlp</li>
           <li>junit-doclet</li>
           <li>latex</li>
           <li>latka</li>
           <li>shell</li>
           <li>struts</li>
           <li>tjdo</li>
+          <li>uberjar  <i>(can be replaced by <a href="http://maven-plugins.sourceforge.net/maven-javaapp-plugin/">javaapp</a>)</i></li>
           <li>vdoclet</li>
           <li>webserver</li>
           <li>wizard</li>

Modified: maven/maven-1/core/trunk/xdocs/roadmap.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/roadmap.xml?rev=378339&r1=378338&r2=378339&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/roadmap.xml (original)
+++ maven/maven-1/core/trunk/xdocs/roadmap.xml Thu Feb 16 10:57:59 2006
@@ -28,8 +28,10 @@
   <body>
     <section name="Roadmap">
       <p>
-        This document details the current high level plans for the Maven project as a whole.
-        More information can be found in JIRA under the
+        This document details the current plans for the Maven 1.X project.
+        Please visit the main <a href="http://maven.apache.org/">Maven</a>
+        page for information on Maven 2.
+        More information on the Maven project as a whole can be found in JIRA under the
         <a href="http://jira.codehaus.org/browse/MPA">MPA</a> project.
       </p>
       <p>
@@ -37,18 +39,23 @@
         also defined in JIRA. For example, the full Maven 1.x roadmap can be browsed under the
         <a href="http://jira.codehaus.org/browse/MAVEN">MAVEN</a> JIRA project.
       </p>
-      <subsection name="Maven 1.1 beta 1">
+      <subsection name="Maven 1.1-beta-3">
         <p>
-          Maven 1.1 beta 1 will be a feature complete version of Maven 1.1. The main objectives of this release are:
+          Maven 1.1-beta-3 will be a feature complete version of Maven 1.1. The main objectives of this release are:
         </p>
         <ul>
           <li>Integration of Maven 2 technologies such as Maven Wagon, Maven SCM and the new model code</li>
           <li>Ant 1.6 support</li>
           <li>Upgrade to later releases of dependencies, in particular Jelly</li>
           <li>Improved POM layout</li>
-          <li>Bugfixes</li>
+          <li>Bugfixes - check the JIRA <a href="http://jira.codehaus.org/browse/MAVEN?report=com.atlassian.jira.plugin.system.project:roadmap-panel">roadmap</a>.</li>
         </ul>
         <p>
+          Maven 1.1-beta-3 will also include an updated version of each core plugin. You can check
+          the current status of plugin development at our
+          <a href="http://docs.codehaus.org/display/MAVEN/Maven+1.1+plugins">confluence page</a>.
+        </p>
+        <p>
           With just a <a href="reference/backwards-compatibility.html">few exceptions</a>, Maven 1.1 will be backwards
           compatible with Maven 1.0.
         </p>
@@ -56,19 +63,6 @@
       <subsection name="Maven 1.1">
         <p>
           After sufficient testing of the beta(s) and at least one release candidate, Maven 1.1 will be released.
-        </p>
-      </subsection>
-      <subsection name="Maven 2.0">
-        <p>
-          Maven 2.0 is a complete rewrite. It will not be backwards compatible with any of the Maven 1.x releases.
-          However it is significantly faster, and has an architecture that supports implementing the popular requested
-          features that Maven 1.x could not. Many of these features, such as transitive dependencies have already been
-          implemented.
-        </p>
-        <p>
-          The alpha releases of Maven 2.0 will not be feature complete and are not expected to be production ready.
-          They will be used as a technology preview, however we will work with early adopters to attempt to maintain
-          backwards compatibility as much as possible.
         </p>
       </subsection>
     </section>