Author: hboutemy
Date: Sun Nov 2 08:16:21 2014
New Revision: 1636088
URL: http://svn.apache.org/r1636088
Log:
wording improvements
Modified:
maven/site/trunk/content/apt/guides/mini/guide-using-toolchains.apt
Modified: maven/site/trunk/content/apt/guides/mini/guide-using-toolchains.apt
URL:
http://svn.apache.org/viewvc/maven/site/trunk/content/apt/guides/mini/guide-using-toolchains.apt?rev=1636088&r1=1636087&r2=1636088&view=diff
==============================================================================
--- maven/site/trunk/content/apt/guides/mini/guide-using-toolchains.apt
(original)
+++ maven/site/trunk/content/apt/guides/mini/guide-using-toolchains.apt Sun Nov
2 08:16:21 2014
@@ -106,17 +106,18 @@ Guide to Using Toolchains
does the plugin know where this JDK is installed? This is where the
<<<toolchains.xml>>> file comes in.
The <<<toolchains.xml>>> file (see below) is the configuration file where
you set the installation paths of your toolchains.
- This file should be put in your <<<${user.home}/.m2>>> directory. When the
<<<maven-toolchains-plugin>>> executes, the <<<maven-toolchain>>> component
- used by the plugin would look for the <<<toolchains.xml>>> file, reads it
and looks for the matching toolchain configured in the
- plugin. In our example, that would be a JDK toolchain with <<<\<version\>>>>
"1.5" and <<<\<vendor\>>>> "sun". Once a match is found,
- the plugin then sets the toolchain to be used in the MavenSession. As you
can see in our <<<toolchains.xml>>> below, there is indeed a JDK
+ This file should be put in your <<<${user.home}/.m2>>> directory. When the
<<<maven-toolchains-plugin>>> executes, it looks for the <<<toolchains.xml>>>
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
+ <<<\<version\>>>> "1.5" and <<<\<vendor\>>>> "sun". Once a match is found,
+ the plugin then stores the toolchain to be used in the MavenSession. As you
can see in our <<<toolchains.xml>>> below, there is indeed a JDK
toolchain with <<<\<version\>>>> "1.5" and <<<\<vendor\>>>> "sun"
configured. So when the <<<maven-compiler-plugin>>> we've
- configured in our <<<pom.xml>>> above executes, it would see that a JDK
toolchain is set in the MavenSession and would thereby use
+ configured in our <<<pom.xml>>> above executes, it will see that a JDK
toolchain is set in the MavenSession and will thereby use
that toolchain (that would be the JDK installed at <<</path/to/jdk/1.5>>>
for our example) to compile the sources.
+-----+
<?xml version="1.0" encoding="UTF8"?>
<toolchains>
+ <!-- JDK toolchains -->
<toolchain>
<type>jdk</type>
<provides>
@@ -139,6 +140,8 @@ Guide to Using Toolchains
<jdkHome>/path/to/jdk/1.6</jdkHome>
</configuration>
</toolchain>
+
+ <!-- other toolchains -->
<toolchain>
<type>netbeans</type>
<provides>
