You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by lt...@apache.org on 2006/04/07 20:48:22 UTC
svn commit: r392361 - in /maven/maven-1/core/trunk/xdocs/using: index.xml
managing-dependencies.xml
Author: ltheussl
Date: Fri Apr 7 11:48:21 2006
New Revision: 392361
URL: http://svn.apache.org/viewcvs?rev=392361&view=rev
Log:
PR: MAVEN-1478
Document plugin dependencies.
Modified:
maven/maven-1/core/trunk/xdocs/using/index.xml
maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml
Modified: maven/maven-1/core/trunk/xdocs/using/index.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/using/index.xml?rev=392361&r1=392360&r2=392361&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/using/index.xml (original)
+++ maven/maven-1/core/trunk/xdocs/using/index.xml Fri Apr 7 11:48:21 2006
@@ -35,11 +35,12 @@
<li><a href="jar.html">Building JARs</a> - How to build an individual library</li>
<li><a href="resources.html">Resources</a> - Adding more files to the generated library</li>
<li><a href="tests.html">Unit Testing</a> - Running unit tests</li>
- <li><a href="war.html">Web Applications</a> - Working with web applications</li>
<li><a href="site.html">Creating a Site</a> - Adding to the project web site</li>
<li><a href="scm.html">Source Control</a> - Working with SCMs</li>
<li><a href="releasing.html">Making Releases</a> - How to cut a release</li>
+ <li><a href="war.html">Web Applications</a> - Working with web applications</li>
<li><a href="multiproject.html">Multiple Modules</a> - Building multiple libraries and applications together</li>
+ <li><a href="managing-dependencies.html">Handling Dependencies</a> - Managing the dependencies of your build</li>
<li><a href="migrating.html">Migrating from Ant</a> - Where to start if you already have <code>build.xml</code></li>
<li><a href="bestpractices.html">Best Practices</a> - Why Maven encourages what it does, and how to take advantage of it</li>
</ul>
@@ -52,6 +53,7 @@
<li><a href="customising.html">Customising Maven</a> - how to change behaviour, add scripting and create
your own plugins</li>
<li><a href="repositories.html">Repositories</a> - how to manage your own artifact repository</li>
+ <li><a href="../reference/index.html">Reference</a> - some quick reference documents</li>
</ul>
</section>
</body>
Modified: maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml
URL: http://svn.apache.org/viewcvs/maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml?rev=392361&r1=392360&r2=392361&view=diff
==============================================================================
--- maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml (original)
+++ maven/maven-1/core/trunk/xdocs/using/managing-dependencies.xml Fri Apr 7 11:48:21 2006
@@ -139,6 +139,27 @@
</p>
</subsection>
+ <subsection name="Plugin Dependencies">
+ <p>
+ It is a little known feature that you can include a dependency
+ on a specific version of a plugin in your <code>project.xml</code>,
+ for example:
+ </p>
+ <source><dependency>
+ <groupId>codeczar-tomcat</group>
+ <artifactId>maven-tomcat-plugin</artifactId>
+ <type>plugin</type>
+ <version>1.1</version>
+</dependency></source>
+ <p>
+ This causes the plugin to be installed into the local repo, and expanded into the cache,
+ but it will not be installed into the maven plugins directory. In other words, your project will
+ use that particular version of the plugin on the fly, without messing up your Maven installation.
+ You may also force other developers to use the same version of the plugin, even if they
+ have a different version of the same plugin installed.
+ </p>
+ </subsection>
+
<subsection name="Keeping Track of Dependencies">
<p>
Maven provides two site reports that can assist in keeping track of dependencies.