You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2019/11/08 14:10:24 UTC

svn commit: r1869561 - in /maven/website/content: guides/mini/guide-configuring-plugins.html maven-site-1.0-site.jar

Author: svn-site-role
Date: Fri Nov  8 14:10:23 2019
New Revision: 1869561

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/mini/guide-configuring-plugins.html
    maven/website/content/maven-site-1.0-site.jar

Modified: maven/website/content/guides/mini/guide-configuring-plugins.html
==============================================================================
--- maven/website/content/guides/mini/guide-configuring-plugins.html (original)
+++ maven/website/content/guides/mini/guide-configuring-plugins.html Fri Nov  8 14:10:23 2019
@@ -429,7 +429,7 @@ public class MyQueryMojo
  * @goal query
  * @phase package
  */
-public class MyBindedQueryMojo
+public class MyBoundQueryMojo
     extends AbstractMojo
 {
     @Parameter(property = "query.url", required = true)
@@ -447,7 +447,7 @@ public class MyBindedQueryMojo
         ...
     }
 }</pre></div>
-<p>From the above mojo example, <code>MyBindedQueryMojo</code> is by default bound to the package phase (see the <code>@phase</code> notation). But if we want to execute this mojo during the install phase and not with package we can rebind this mojo into a new lifecycle phase using the <code>&lt;phase&gt;</code> tag under <code>&lt;execution&gt;</code>.</p>
+<p>From the above mojo example, <code>MyBoundQueryMojo</code> is by default bound to the package phase (see the <code>@phase</code> notation). But if we want to execute this mojo during the install phase and not with package we can rebind this mojo into a new lifecycle phase using the <code>&lt;phase&gt;</code> tag under <code>&lt;execution&gt;</code>.</p>
 <div class="source"><pre class="prettyprint linenums">&lt;project&gt;
   ...
   &lt;build&gt;
@@ -478,7 +478,7 @@ public class MyBindedQueryMojo
   &lt;/build&gt;
   ...
 &lt;/project&gt;</pre></div>
-<p>Now, <code>MyBindedQueryMojo</code> default phase which is package has been overridden by install phase.</p>
+<p>Now, <code>MyBoundQueryMojo</code> default phase which is package has been overridden by install phase.</p>
 <p><b>Note:</b> Configurations inside the <code>&lt;executions&gt;</code> element used to differ from those that are outside <code>&lt;executions&gt;</code> 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></section><section>
 <h4><a name="Using_the_.3Cdependencies.3E_Tag"></a><a name="Using_the_dependencies_Tag">Using the <code>&lt;dependencies&gt;</code> Tag</a></h4>

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