You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ar...@apache.org on 2006/02/14 08:06:51 UTC

svn commit: r377658 - /maven/site/trunk/src/site/apt/guides/mini/guide-configuring-plugins.apt

Author: aramirez
Date: Mon Feb 13 23:06:50 2006
New Revision: 377658

URL: http://svn.apache.org/viewcvs?rev=377658&view=rev
Log:
-fixed indention

Modified:
    maven/site/trunk/src/site/apt/guides/mini/guide-configuring-plugins.apt

Modified: maven/site/trunk/src/site/apt/guides/mini/guide-configuring-plugins.apt
URL: http://svn.apache.org/viewcvs/maven/site/trunk/src/site/apt/guides/mini/guide-configuring-plugins.apt?rev=377658&r1=377657&r2=377658&view=diff
==============================================================================
--- maven/site/trunk/src/site/apt/guides/mini/guide-configuring-plugins.apt (original)
+++ maven/site/trunk/src/site/apt/guides/mini/guide-configuring-plugins.apt Mon Feb 13 23:06:50 2006
@@ -234,7 +234,8 @@
 
 * Using the executions tag
 
-You can also configure a mojo using the executions tag. Using MyQueryMojo as an example, you may have something that will look like:
+  You can also configure a mojo using the executions tag. Using MyQueryMojo 
+  as an example, you may have something that will look like:
 
 +----+
 <project>
@@ -277,19 +278,19 @@
 </project>
 +----+
 
-The first execution with id "execution1" binds this configuration to the test 
-phase. Some goals can have default phases. The second execution does not have 
-a <phase> tag, how do you think will the execution behave? If the goal is
-binded to a phase then it will execute to that phase. But if the goal is 
-not binded to any lifecycle phases then it will be executed without executing 
-any phases(as if it was executed in the CLI).
-
-Note that execution id's don't have to be unique.  Executions of the same id 
-are merged. 
-
-How about if we have a multiple executions with different phases bound to it? 
-How do you think will it behave? Let us use the example POM above again, but 
-this time we shall bind <<<execution2>>> to a phase.
+  The first execution with id "execution1" binds this configuration to the test 
+  phase. Some goals can have default phases. The second execution does not have 
+  a <phase> tag, how do you think will the execution behave? If the goal is
+  binded to a phase then it will execute to that phase. But if the goal is 
+  not binded to any lifecycle phases then it will be executed without executing 
+  any phases(as if it was executed in the CLI).
+
+  Note that execution id's don't have to be unique.  Executions of the same id 
+  are merged. 
+
+  How about if we have a multiple executions with different phases bound to it? 
+  How do you think will it behave? Let us use the example POM above again, but 
+  this time we shall bind <<<execution2>>> to a phase.
 
 +----+
 <project>
@@ -325,15 +326,15 @@
 </project>
 +----+
 
-If there are multiple executions bound to different phases, then the mojo is 
-executed once for each phase indicated. Meaning, <<<execution1>>> will be 
-executed applying the configuration setup when the phase of the build is test, 
-and <<<execution2>>> will be executed applying the configuration setup when 
-the build phase is already in install.
-
-Configurations inside the <executions> tag differ from those that are outside 
-<executions> 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.
+  If there are multiple executions bound to different phases, then the mojo is 
+  executed once for each phase indicated. Meaning, <<<execution1>>> will be 
+  executed applying the configuration setup when the phase of the build is test, 
+  and <<<execution2>>> will be executed applying the configuration setup when 
+  the build phase is already in install.
+
+  Configurations inside the <executions> tag differ from those that are outside 
+  <executions> 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.