svn commit: r1010264 - in /websites/staging/maven/trunk/content: ./ guides/mini/guide-configuring-plugins.html maven-site-1.0-site.jar

[bu...@apache.org]

Author: buildbot
Date: Tue Apr 11 20:20:28 2017
New Revision: 1010264

Log:
Staging update by buildbot for maven

Modified:
    websites/staging/maven/trunk/content/   (props changed)
    websites/staging/maven/trunk/content/guides/mini/guide-configuring-plugins.html
    websites/staging/maven/trunk/content/maven-site-1.0-site.jar

Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Apr 11 20:20:28 2017
@@ -1 +1 @@
-1791009
+1791023

Modified: websites/staging/maven/trunk/content/guides/mini/guide-configuring-plugins.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-configuring-plugins.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-configuring-plugins.html Tue Apr 11 20:20:28 2017
@@ -495,7 +495,8 @@ public class MyBindedQueryMojo
   ...
 &lt;/project&gt;</pre></div>
 <p>Now, <tt>MyBindedQueryMojo</tt> default phase which is package has been overrided by install phase.</p>
-<p><b>Note:</b> Configurations inside the <tt>&lt;executions&gt;</tt> tag differ from those that are outside <tt>&lt;executions&gt;</tt> in that they cannot be used from a direct command line invocation. Instead they are only applied when the lifecycle phase they are bound to are invoked. Alternatively, if you move a configuration section outside of the executions section, it will apply globally to all invocations of the plugin.</p></div>
+<p><b>Note:</b> Configurations inside the <tt>&lt;executions&gt;</tt> element used to differ from those that are outside <tt>&lt;executions&gt;</tt> in that they could not be used from a direct command line invocation because they were only applied when the lifecycle phase they were bound to was invoked. So you had to move a configuration section outside of the executions section to apply it globally to all invocations of the plugin. Since Maven 3.3.1 this is not the case anymore as you can specify on the command line the execution id for direct plugin goal invocation. Hence if you want to run the above plugin and it's specific execution1's configuration from the command-line, you can execute:</p>
+<div class="source"><pre class="prettyprint linenums">mvn myqyeryplugin:queryMojo@execution1</pre></div></div>
 <div class="section">
 <h4><a name="Using_the_dependencies_Tag">Using the <tt>&lt;dependencies&gt;</tt> Tag</a></h4>
 <p>You could configure the dependencies of the Build plugins, commonly to use a more recent dependency version.</p>

Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.