You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ah...@apache.org on 2006/08/02 00:42:10 UTC
svn commit: r427777 -
/maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml
Author: aheritier
Date: Tue Aug 1 15:42:09 2006
New Revision: 427777
URL: http://svn.apache.org/viewvc?rev=427777&view=rev
Log:
Fix grammar, ...
Modified:
maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml
Modified: maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml
URL: http://svn.apache.org/viewvc/maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml?rev=427777&r1=427776&r2=427777&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml (original)
+++ maven/maven-1/core/trunk/xdocs/reference/backwards-compatibility.xml Tue Aug 1 15:42:09 2006
@@ -85,7 +85,7 @@
<li>junit-doclet</li>
<li>latex</li>
<li>latka</li>
- <li>release <i>(replaced functionality by scm)</i></li>
+ <li>release <i>(replaced by <a href="http://maven.apache.org/maven-1.x/plugins/scm/">scm plugin</a>)</i></li>
<li>repository</li>
<li>shell</li>
<li>struts</li>
@@ -148,8 +148,8 @@
or fields such as <code>scmType</code>, which depended on the split function, are missing.
</p>
<p>
- <b>Fix:</b> These functions have been removed. The static methods do exist in
- <code>maven-changelog-plugin</code> if needed, in the <code>RepositoryUtils</code> class.
+ <b>Fix:</b>The static methods have been removed from the core
+ but they exist in the <code>RepositoryUtils</code> class in <code>maven-changelog-plugin</code> if needed.
All other plugins had been manually splitting the connection string.
See <code>maven-scm-plugin</code> for an example of this.
The future should see all plugins and code using Maven SCM for this task, and all dealings with an
@@ -174,7 +174,7 @@
<dt>POM and Entities</dt>
<dd>
<p>
- Due to a bug in the new model generated by modello (See <a href="http://jira.codehaus.org/browse/MAVEN-1755">MAVEN-1755</a>) relative SYSTEM entities not work in the POM.
+ Due to a bug in the new model generated by modello (See <a href="http://jira.codehaus.org/browse/MAVEN-1755">MAVEN-1755</a>) relative SYSTEM entities do not work in the POM.
</p>
</dd>
</dl>
@@ -187,9 +187,9 @@
another version of xml-apis in your tests, you have to fork the JVM.
</p>
<p>
- If in a custom goal or in a plugin, you use some xslt transformations, we recommend to not
- use the style task in ant which will not work with all JDKs. Instead of that you are
- encouraged to use a custom process launched in a forked JVM (like it's done in the PDF plugin
+ If in a custom goal or in a plugin, you use some xslt transformations, we recommend that you not
+ use the style task in ant which will not work with all JDKs. Instead, you are encouraged
+ to use a custom process launched in a forked JVM (like it's done in the PDF plugin
for example).
</p>
</dd>
@@ -257,9 +257,9 @@
another version of xml-apis in your tests, you have to fork the JVM.
</p>
<p>
- If in a custom goal or in a plugin, you use some xslt transformations, we recommend to not
- use the style task in ant which will not work with all JDKs. Instead of that you are
- encouraged to use a custom process launched in a forked JVM (Like it's done in the PDF plugin
+ If in a custom goal or in a plugin, you use some xslt transformations, we recommend that you not
+ use the style task in ant which will not work with all JDKs. Instead, you are encouraged to use
+ a custom process launched in a forked JVM (Like it's done in the PDF plugin
for example).
</p>
</dd>
@@ -271,7 +271,7 @@
With the upgrade of Dom4J, relative SYSTEM entities work in xdocs and maven.xml.
Due to a bug in the new model generated by modello
(See <a href="http://jira.codehaus.org/browse/MAVEN-1755">MAVEN-1755</a>) relative
- SYSTEM entities not work in the POM.
+ SYSTEM entities do not work in the POM.
</p>
</dd>
</dl>