You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by br...@apache.org on 2010/03/01 00:21:54 UTC
svn commit: r917321 - in /maven/site/trunk/src/site/apt:
docs/2.0.10/release-notes.txt docs/2.0.9/release-notes.txt
docs/2.2.0/release-notes.txt guides/mini/guide-site.apt run-maven/index.apt
Author: brett
Date: Sun Feb 28 23:21:53 2010
New Revision: 917321
URL: http://svn.apache.org/viewvc?rev=917321&view=rev
Log:
fix issues reported by linkcheck plugin
Modified:
maven/site/trunk/src/site/apt/docs/2.0.10/release-notes.txt
maven/site/trunk/src/site/apt/docs/2.0.9/release-notes.txt
maven/site/trunk/src/site/apt/docs/2.2.0/release-notes.txt
maven/site/trunk/src/site/apt/guides/mini/guide-site.apt
maven/site/trunk/src/site/apt/run-maven/index.apt
Modified: maven/site/trunk/src/site/apt/docs/2.0.10/release-notes.txt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/docs/2.0.10/release-notes.txt?rev=917321&r1=917320&r2=917321&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/docs/2.0.10/release-notes.txt (original)
+++ maven/site/trunk/src/site/apt/docs/2.0.10/release-notes.txt Sun Feb 28 23:21:53 2010
@@ -8,7 +8,7 @@
This release was extensively screened for regressions with Release Candidates but several things are worth noting.
- * MNG-3974 - The mirror syntax order did not match the documentation. In 2.0.9, the last mirror that matched a repository would win. The correct behavior in 2.0.10 is the first match wins. Using the syntax that lets you exclude a repository from a match (*,!notthisone,thisone), it should always be possible to ensure your matching is deterministic regardless of order. See the settings {{{./settings.html#Mirrors}specification}} for more information.
+ * MNG-3974 - The mirror syntax order did not match the documentation. In 2.0.9, the last mirror that matched a repository would win. The correct behavior in 2.0.10 is the first match wins. Using the syntax that lets you exclude a repository from a match (*,!notthisone,thisone), it should always be possible to ensure your matching is deterministic regardless of order. See the settings {{{/settings.html#Mirrors}specification}} for more information.
* MNG-3424 - in 2.0.9 we made the dependency order deterministic using linkedHashMaps, in 2.0.10, the rest of the hashMaps in the pom model have been replaced with linkedHashMaps. This may cause subtle changes in the ordering of executions or other processing since 2.0.9. The fix would be to reorder the elements that cause problems, and know that it will be predictable from now on.
Modified: maven/site/trunk/src/site/apt/docs/2.0.9/release-notes.txt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/docs/2.0.9/release-notes.txt?rev=917321&r1=917320&r2=917321&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/docs/2.0.9/release-notes.txt (original)
+++ maven/site/trunk/src/site/apt/docs/2.0.9/release-notes.txt Sun Feb 28 23:21:53 2010
@@ -21,13 +21,13 @@
* MNG-3286 - The inherited field in a plugin execution block is now functioning correctly. Previously you could only dis-inherit an entire plugin configuration.
- * MNG-3220 - There is now a new scope for importing managed dependencies. See {{{http://docs.codehaus.org/display/MAVEN/Importing+Managed+Dependencies}here}} and {{{./guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies}here}} for details. Please note that the use of this scope will break backwards compatibility with older Maven versions. If you use this, you should use the maven-enforcer-plugin to require a minimum maven version of 2.0.9
+ * MNG-3220 - There is now a new scope for importing managed dependencies. See {{{http://docs.codehaus.org/display/MAVEN/Importing+Managed+Dependencies}here}} and {{{/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies}here}} for details. Please note that the use of this scope will break backwards compatibility with older Maven versions. If you use this, you should use the maven-enforcer-plugin to require a minimum maven version of 2.0.9
* MNG-3394 - plugin versions specified in pluginManagement are now properly overriden by build.plugin.version specification.
* MNG-3415 - Transmission errors when downloading artifacts should not corrupt the local repository metadata. Hopefully this means the end of "delete your local repo" as a debug step.
- * MNG-3461 - There is a new, more flexible way to define mirror settings. See the settings {{{./settings.html#Mirrors}specification}} for more information.
+ * MNG-3461 - There is a new, more flexible way to define mirror settings. See the settings {{{/settings.html#Mirrors}specification}} for more information.
** Plugin Versions defined in the 2.0.9 super pom:
Modified: maven/site/trunk/src/site/apt/docs/2.2.0/release-notes.txt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/docs/2.2.0/release-notes.txt?rev=917321&r1=917320&r2=917321&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/docs/2.2.0/release-notes.txt (original)
+++ maven/site/trunk/src/site/apt/docs/2.2.0/release-notes.txt Sun Feb 28 23:21:53 2010
@@ -6,7 +6,7 @@
** Changes that may affect existing builds
- * MNG-4143 - Starting in 2.2.0, Maven will run only on Java 1.5 and later. You can still build projects for JDK1.4 and earlier using the approach documented in the {{{./guides/mini/guide-building-jdk14-on-jdk15.html}Guide to Building JDK 1.4 Projects on JDK 1.5}}.
+ * MNG-4143 - Starting in 2.2.0, Maven will run only on Java 1.5 and later. You can still build projects for JDK1.4 and earlier using the approach documented in the {{{/guides/mini/guide-building-jdk14-on-jdk15.html}Guide to Building JDK 1.4 Projects on JDK 1.5}}.
* MNG-3401 - Executions with an id equal to <<<default->>><phase> (where <phase> is a valid lifecycle phase) may have unexpected results as it will be merged into the default lifecycle.
@@ -14,9 +14,9 @@
** Noteworthy changes and improvements
- * MNG-3401 - Starting in Maven 2.2.0, goals invoked directly from the command line can be configured in the POM separately from other plugin invocations using a special executionId called <<<default-cli>>>. Where previously, all configurations for command-line goals had to go in the plugin-level configuration, Maven 2.2.0 allows command-line-specific configurations to be separated into their own <<<\<execution\>>>>. For more information, see the {{{./guides/mini/guide-default-execution-ids.html}Guide to Default Execution IDs}}.
+ * MNG-3401 - Starting in Maven 2.2.0, goals invoked directly from the command line can be configured in the POM separately from other plugin invocations using a special executionId called <<<default-cli>>>. Where previously, all configurations for command-line goals had to go in the plugin-level configuration, Maven 2.2.0 allows command-line-specific configurations to be separated into their own <<<\<execution\>>>>. For more information, see the {{{/guides/mini/guide-default-execution-ids.html}Guide to Default Execution IDs}}.
- * MNG-3203 - Similar to MNG-3401, previous to Maven 2.2.0 it was impossible to separate configurations for different goals from a single plugin that were bound to the lifecycle by the default mappings for a given packaging. Beginning in Maven 2.2.0, it is possible to separate configurations for <<<compiler:compile>>> from those for <<<compiler:testCompile>>> using executions with IDs <<<default-compile>>> and <<<default-testCompile>>> respectively. In the case of the compiler plugin, this allows the separation of include and exclude patterns that are applied during the two compiler activities in the <<<jar>>> build. For more information, see the {{{./guides/mini/guide-default-execution-ids.html}Guide to Default Execution IDs}}.
+ * MNG-3203 - Similar to MNG-3401, previous to Maven 2.2.0 it was impossible to separate configurations for different goals from a single plugin that were bound to the lifecycle by the default mappings for a given packaging. Beginning in Maven 2.2.0, it is possible to separate configurations for <<<compiler:compile>>> from those for <<<compiler:testCompile>>> using executions with IDs <<<default-compile>>> and <<<default-testCompile>>> respectively. In the case of the compiler plugin, this allows the separation of include and exclude patterns that are applied during the two compiler activities in the <<<jar>>> build. For more information, see the {{{/guides/mini/guide-default-execution-ids.html}Guide to Default Execution IDs}}.
* MNG-4179 - <<Regression:>> In Maven 2.1.0, artifact downloads hang when a transfer failure occurred. This has been corrected.
Modified: maven/site/trunk/src/site/apt/guides/mini/guide-site.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/guides/mini/guide-site.apt?rev=917321&r1=917320&r2=917321&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-site.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-site.apt Sun Feb 28 23:21:53 2010
@@ -38,7 +38,7 @@
has been replaced by the site descriptor (see below).
The APT format, "Almost Plain Text", is a wiki-like format that allows you to write simple, structured documents (like this one)
- very quickly. A full reference of the {{{./guide-apt-format.html} APT Format}} is available.
+ very quickly. A full reference of the {{{http://maven.apache.org/doxia/references/apt-format.html} APT Format}} is available.
The FML format is the FAQ format, also used in Maven 1.x.
Modified: maven/site/trunk/src/site/apt/run-maven/index.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/run-maven/index.apt?rev=917321&r1=917320&r2=917321&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/run-maven/index.apt (original)
+++ maven/site/trunk/src/site/apt/run-maven/index.apt Sun Feb 28 23:21:53 2010
@@ -62,8 +62,6 @@
Maven can do more than just build software - it can assist with testing, run web applications and produce reports on
projects, as well as any number of other tasks provided by plug-ins.
- To try some other tasks, see the {{{./cookbook/index.html} Cookbook for Running Maven}}.
-
** When Things go Wrong
The following are some common problems when building with Maven, and how to resolve them.