svn commit: r790061 - /maven/site/trunk/src/site/apt/release-notes.apt.vm

[be...@apache.org]

Author: bentmann
Date: Wed Jul  1 08:23:59 2009
New Revision: 790061

URL: http://svn.apache.org/viewvc?rev=790061&view=rev
Log:
o Fixed typo

Modified:
    maven/site/trunk/src/site/apt/release-notes.apt.vm

Modified: maven/site/trunk/src/site/apt/release-notes.apt.vm
URL: http://svn.apache.org/viewvc/maven/site/trunk/src/site/apt/release-notes.apt.vm?rev=790061&r1=790060&r2=790061&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/release-notes.apt.vm (original)
+++ maven/site/trunk/src/site/apt/release-notes.apt.vm Wed Jul  1 08:23:59 2009
@@ -65,7 +65,7 @@
 
     * 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 froma 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.