svn commit: r325844 - /maven/maven-1/core/trunk/xdocs/using/developing-plugins.xml

[ah...@apache.org]

Author: aheritier
Date: Sun Oct 16 22:31:44 2005
New Revision: 325844

URL: http://svn.apache.org/viewcvs?rev=325844&view=rev
Log:
Minor fix

Modified:
    maven/maven-1/core/trunk/xdocs/using/developing-plugins.xml

Modified: maven/maven-1/core/trunk/xdocs/using/developing-plugins.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/using/developing-plugins.xml?rev=325844&r1=325843&r2=325844&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/using/developing-plugins.xml (original)
+++ maven/maven-1/core/trunk/xdocs/using/developing-plugins.xml Sun Oct 16 22:31:44 2005
@@ -144,6 +144,7 @@
           For more information, please refer to <a href="../reference/scripting.html">Scripting in Maven</a>.
         </p>
       </subsection>
+
       <subsection name="Using Plugin Properties">
         <p>
           While you can always reference the POM information in a Jelly script using <code>${pom.artifactId}</code>,
@@ -179,6 +180,7 @@
           The order of precedence is given in the <a href="../reference/properties.html">Properties Reference</a>.
         </p>
       </subsection>
+
       <subsection name="Using Plugin Resources">
         <p>
           You can use plugin resources to be able to load external files from inside a plugin.
@@ -217,7 +219,7 @@
           <li>root.maven (child of root) : Where are loaded (by default) all others dependencies needed by maven, its plugins and the user project.</li>
         </ul>
         <p>
-          Thus, this design can create 2 problems when you write your own plugin :
+          This design can create 2 problems when you write your own plugin :
         </p>
         <ol>
           <li>You won't be able to use your own version of a dependency. If this one is already loaded by maven or one of its plugins in a different version you'll automatically use it. To avoid having this sort of problem, you are invited to use in priority the libraries versions already used <a href="../dependencies.html">by maven</a> or <a href="../reference/plugins/dependency-convergence-report.html">by the bundled plugins</a>.</li>