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 bu...@apache.org on 2014/10/30 10:32:36 UTC
svn commit: r927385 - in /websites/staging/maven/trunk/content: ./
guides/mini/guide-using-toolchains.html maven-site-1.0-site.jar
Author: buildbot
Date: Thu Oct 30 09:32:36 2014
New Revision: 927385
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/guides/mini/guide-using-toolchains.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 Thu Oct 30 09:32:36 2014
@@ -1 +1 @@
-1635432
+1635441
Modified: websites/staging/maven/trunk/content/guides/mini/guide-using-toolchains.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-using-toolchains.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-using-toolchains.html Thu Oct 30 09:32:36 2014
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../../css/print.css" type="text/css" media="print" />
<meta name="author" content="Maria Odea Ching" />
- <meta name="Date-Creation-yyyymmdd" content="20080725" />
+ <meta name="Date-Creation-yyyymmdd" content="20141030" />
<meta name="Date-Revision-yyyymmdd" content="20141030" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -245,20 +245,21 @@
<h2><a name="Guide_to_Using_Toolchains"></a>Guide to Using Toolchains</h2>
<div class="section">
<h3><a name="What_is_Toolchains"></a>What is Toolchains?</h3>
-<p>The Maven Toolchains provide a way for plugins to discover what JDK (or other tools) are to be used during the build, without the need to configure them. With toolchains, a project can now be built using a specific version of JDK independent from the one Maven is running with. (Think how JDK versions can be set in IDEs like Idea, NetBeans and Eclipse)</p>
-<p>Toolchains would only work in Maven 2.0.9 and higher versions. For more details about it's design and implementation, please see <a class="externalLink" href="http://cwiki.apache.org/confluence/display/MAVENOLD/Toolchains">Toolchains</a>.</p>
-<p>Below are the plugins which are toolchain-aware, meaning they can be used with toolchains:</p>
+<p>The Maven Toolchains provide a way for plugins to discover what JDK (or other tools) are to be used during the build, without the need to configure them in each plugin nor in every <tt>pom.xml</tt>, or forcing a precise location among every machine building the project.</p>
+<p>With Maven Toolchains, a project can now be built using a specific version of JDK independent from the one Maven is running with. Think how JDK versions can be set in IDEs like Idea, NetBeans and Eclipse, or how you can build with an older JDK from Maven running with a recent one.</p>
+<p>Toolchains will only work in Maven 2.0.9 and higher versions. For more details about its design and implementation, please see <a class="externalLink" href="http://cwiki.apache.org/confluence/display/MAVENOLD/Toolchains">Toolchains</a>.</p>
+<p>Below are some plugins which are JDK-toolchain-aware, meaning they can use any JDK configured with toolchains:</p>
<ol style="list-style-type: decimal">
-<li><tt>maven-compiler-plugin</tt>, starting with 2.1,</li>
-<li><tt>maven-javadoc-plugin</tt>, starting with 2.5,</li>
-<li><tt>maven-surefire-plugin</tt>, starting with 2.5,</li>
-<li><tt>exec-maven-plugin</tt> (Codehaus MOJO), starting with 1.1.1.</li></ol></div>
+<li><tt><a href="/plugins/maven-compiler-plugin/">maven-compiler-plugin</a></tt>, starting with 2.1,</li>
+<li><tt><a href="/plugins/maven-javadoc-plugin/">maven-javadoc-plugin</a></tt>, starting with 2.5,</li>
+<li><tt><a href="/plugins/maven-surefire-plugin/">maven-surefire-plugin</a></tt>, starting with 2.5,</li>
+<li><tt><a class="externalLink" href="http://mojo.codehaus.org/exec-maven-plugin/">exec-maven-plugin</a></tt> (Codehaus MOJO), starting with 1.1.1.</li></ol></div>
<div class="section">
<h3><a name="Using_Toolchains_in_Your_Project"></a>Using Toolchains in Your Project</h3>
<p>There are two essential components that you need to configure in order to use toolchains:</p>
<ol style="list-style-type: decimal">
-<li>the <tt><a href="/plugins/maven-toolchains-plugin/">maven-toolchains-plugin</a></tt>,</li>
-<li>the <tt><a href="/ref/current/maven-core/toolchains.html">toolchains.xml</a></tt> file.</li></ol>
+<li>the <tt><a href="/plugins/maven-toolchains-plugin/">maven-toolchains-plugin</a></tt> in your project POM,</li>
+<li>the <tt><a href="/ref/current/maven-core/toolchains.html">toolchains.xml</a></tt> file on the building machine.</li></ol>
<p>The <tt>maven-toolchains-plugin</tt> is the one that sets the toolchain to be used by the toolchain-aware plugins in your project.</p>
<p>For example, you want to use a different JDK version to build your project than the version used to run Maven, you can configure the version you want to use via this plugin as shown in the <tt>pom.xml</tt> below:</p>
<div class="source">
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.