svn commit: r994611 - in /websites/staging/maven/trunk/content: ./ guides/mini/guide-using-toolchains.html maven-site-1.0-site.jar

[bu...@apache.org]

Author: buildbot
Date: Sat Aug  6 16:35:34 2016
New Revision: 994611

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 Sat Aug  6 16:35:34 2016
@@ -1 +1 @@
-1755404
+1755405

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 Sat Aug  6 16:35:34 2016
@@ -227,7 +227,7 @@ Karl Heinz Marbaise" />
 &lt;/plugins&gt;</pre></div>
 <p>As you can see in the example above, a JDK toolchain with <tt>&lt;version&gt;</tt> &quot;1.5&quot; and <tt>&lt;vendor&gt;</tt> &quot;sun&quot; is to be used. Now how does the plugin know where this JDK is installed? This is where the <tt>toolchains.xml</tt> file comes in.</p>
 <p>The <tt>toolchains.xml</tt> file (see below) is the configuration file where you set the installation paths of your toolchains. This file should be put in your <tt>${user.home}/.m2</tt> directory. When the <tt>maven-toolchains-plugin</tt> executes, it looks for the <tt>toolchains.xml</tt> file, reads it and looks for a toolchain matching the toolchains requirements configured in the plugin. In our example, that would be a JDK toolchain with <tt>&lt;version&gt;</tt> &quot;1.5&quot; and <tt>&lt;vendor&gt;</tt> &quot;sun&quot;. Once a match is found, the plugin then stores the toolchain to be used in the MavenSession. As you can see in our <tt>toolchains.xml</tt> below, there is indeed a JDK toolchain with <tt>&lt;version&gt;</tt> &quot;1.5&quot; and <tt>&lt;vendor&gt;</tt> &quot;sun&quot; configured. So when the <tt>maven-compiler-plugin</tt> we've configured in our <tt>pom.xml</tt> above executes, it will see that a JDK toolchain is set in the MavenSession and will thereby use tha
 t toolchain (that would be the JDK installed at <tt>/path/to/jdk/1.5</tt> for our example) to compile the sources.</p>
-<p>Starting with <a href="./docs/3.3.1/release-notes.html">Maven 3.3.1</a> you can put the <tt>toolchains.xml</tt> file wherever you like by using the <tt>--global-toolchains file</tt> option but it is recommended to locate it into <tt>${user.home}/.m2/</tt>. </p>
+<p>Starting with <a href="/docs/3.3.1/release-notes.html">Maven 3.3.1</a> you can put the <tt>toolchains.xml</tt> file wherever you like by using the <tt>--global-toolchains file</tt> option but it is recommended to locate it into <tt>${user.home}/.m2/</tt>. </p>
 <div class="source"><pre class="prettyprint linenums">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF8&quot;?&gt;
 &lt;toolchains&gt;
   &lt;!-- JDK toolchains --&gt;

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