Author: buildbot
Date: Thu May 12 22:17:00 2016
New Revision: 988091
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/guides/development/guide-testing-development-plugins.html
websites/staging/maven/trunk/content/guides/getting-started/index.html
websites/staging/maven/trunk/content/guides/introduction/introduction-to-plugin-prefix-mapping.html
websites/staging/maven/trunk/content/guides/introduction/introduction-to-profiles.html
websites/staging/maven/trunk/content/guides/mini/guide-encryption.html
websites/staging/maven/trunk/content/guides/mini/guide-multiple-repositories.html
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 May 12 22:17:00 2016
@@ -1 +1 @@
-1743586
+1743587
Modified:
websites/staging/maven/trunk/content/guides/development/guide-testing-development-plugins.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/development/guide-testing-development-plugins.html
(original)
+++
websites/staging/maven/trunk/content/guides/development/guide-testing-development-plugins.html
Thu May 12 22:17:00 2016
@@ -492,7 +492,7 @@
<div class="section">
<h3><a name="Using_Settings_without_Modifying_the_Project"></a>Using Settings
without Modifying the Project</h3>
<p>If you are using the goals from the command line on a number of projects,
you should include this in your <tt>settings.xml</tt> file instead.</p>
-<p>You need to modify your <tt>~/.m2/settings.xml</tt> file to include two new
profiles and then when you need access to the plugin snapshots use
<tt>-Papache</tt>. The profile only needs to be enabled once so that the
plugins can be downloaded into you local repository. Once in your local
repository Maven can succesfully resolve the dependencies and the profile no
longer needs to be activated.</p>
+<p>You need to modify your <tt>${user.home}/.m2/settings.xml</tt> file to
include two new profiles and then when you need access to the plugin snapshots
use <tt>-Papache</tt>. The profile only needs to be enabled once so that the
plugins can be downloaded into you local repository. Once in your local
repository Maven can succesfully resolve the dependencies and the profile no
longer needs to be activated.</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
<profiles>
Modified: websites/staging/maven/trunk/content/guides/getting-started/index.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/getting-started/index.html
(original)
+++ websites/staging/maven/trunk/content/guides/getting-started/index.html Thu
May 12 22:17:00 2016
@@ -658,7 +658,7 @@ Results :
<p>Making a JAR file is straight forward enough and can be accomplished by
executing the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn package</pre></div>
<p>If you take a look at the POM for your project you will notice the
<tt>packaging</tt> element is set to <tt>jar</tt>. This is how Maven knows to
produce a JAR file from the above command (we'll talk more about this later).
You can now take a look in the <tt>${basedir}/target</tt> directory and you
will see the generated JAR file.</p>
-<p>Now you'll want to install the artifact you've generated (the JAR file) in
your local repository (<tt>~/.m2/repository</tt> is the default location). For
more information on repositories you can refer to our <a
href="../introduction/introduction-to-repositories.html">Introduction to
Repositories</a> but let's move on to installing our artifact! To do so execute
the following command:</p>
+<p>Now you'll want to install the artifact you've generated (the JAR file) in
your local repository (<tt>${user.home}/.m2/repository</tt> is the default
location). For more information on repositories you can refer to our <a
href="../introduction/introduction-to-repositories.html">Introduction to
Repositories</a> but let's move on to installing our artifact! To do so execute
the following command:</p>
<div class="source"><pre class="prettyprint linenums">mvn install</pre></div>
<p>Upon executing this command you should see the following output:</p>
<div class="source"><pre class="prettyprint linenums">[INFO]
----------------------------------------------------------------------------
@@ -988,7 +988,7 @@ command.line.prop=${command.line.prop}</
</project></pre></div>
<p>For each external dependency, you'll need to define at least 4 things:
groupId, artifactId, version, and scope. The groupId, artifactId, and version
are the same as those given in the <tt>pom.xml</tt> for the project that built
that dependency. The scope element indicates how your project uses that
dependency, and can be values like <tt>compile</tt>, <tt>test</tt>, and
<tt>runtime</tt>. For more information on everything you can specify for a
dependency, see the <a href="/ref/current/maven-model/maven.html">Project
Descriptor Reference</a>.</p>
<p>For more information about the dependency mechanism as a whole, see <a
href="../introduction/introduction-to-dependency-mechanism.html">Introduction
to Dependency Mechanism</a>.</p>
-<p>With this information about a dependency, Maven will be able to reference
the dependency when it builds the project. Where does Maven reference the
dependency from? Maven looks in your local repository
(<tt>~/.m2/repository</tt> is the default location) to find all dependencies.
In a <a
href="#How_do_I_create_a_JAR_and_install_it_in_my_local_repository">previous
section</a>, we installed the artifact from our project
(my-app-1.0-SNAPSHOT.jar) into the local repository. Once it's installed there,
another project can reference that jar as a dependency simply by adding the
dependency information to its pom.xml:</p>
+<p>With this information about a dependency, Maven will be able to reference
the dependency when it builds the project. Where does Maven reference the
dependency from? Maven looks in your local repository
(<tt>${user.home}/.m2/repository</tt> is the default location) to find all
dependencies. In a <a
href="#How_do_I_create_a_JAR_and_install_it_in_my_local_repository">previous
section</a>, we installed the artifact from our project
(my-app-1.0-SNAPSHOT.jar) into the local repository. Once it's installed there,
another project can reference that jar as a dependency simply by adding the
dependency information to its pom.xml:</p>
<div class="source"><pre class="prettyprint linenums"><project
xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
Modified:
websites/staging/maven/trunk/content/guides/introduction/introduction-to-plugin-prefix-mapping.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/introduction/introduction-to-plugin-prefix-mapping.html
(original)
+++
websites/staging/maven/trunk/content/guides/introduction/introduction-to-plugin-prefix-mapping.html
Thu May 12 22:17:00 2016
@@ -481,7 +481,7 @@
<div class="section">
<h3><a name="Configuring_Maven_to_Search_for_Plugins"></a>Configuring Maven to
Search for Plugins</h3>
<p>By default, Maven will search the groupId <b>org.apache.maven.plugins</b>
for prefix-to-artifactId mappings for the plugins it needs to perform a given
build. However, as previously mentioned, the user may have a need for
third-party plugins. Since the Maven project is assumed to have control over
the default plugin groupId, this means configuring Maven to search other
groupId locations for plugin-prefix mappings.</p>
-<p>As it turns out, this is simple. In the Maven settings file (per-user:
<tt>~/.m2/settings.xml</tt>; global: <tt>${maven.home}/conf/settings.xml</tt>),
you can provide a custom <b>pluginGroups</b> section, listing the plugin
groupIds you want to search (each groupId goes in its own <b>pluginGroup</b>
sub-element). For example, if my project uses a Modello model file, I might
have the following in my settings:</p>
+<p>As it turns out, this is simple. In the Maven settings file (per-user:
<tt>${user.home}/.m2/settings.xml</tt>; global:
<tt>${maven.home}/conf/settings.xml</tt>), you can provide a custom
<b>pluginGroups</b> section, listing the plugin groupIds you want to search
(each groupId goes in its own <b>pluginGroup</b> sub-element). For example, if
my project uses a Modello model file, I might have the following in my
settings:</p>
<div class="source"><pre class="prettyprint linenums"><pluginGroups>
<pluginGroup>org.codehaus.modello</pluginGroup>
</pluginGroups></pre></div>
Modified:
websites/staging/maven/trunk/content/guides/introduction/introduction-to-profiles.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/introduction/introduction-to-profiles.html
(original)
+++
websites/staging/maven/trunk/content/guides/introduction/introduction-to-profiles.html
Thu May 12 22:17:00 2016
@@ -623,7 +623,7 @@
</build>
...
</project></pre></div>
-<p>Now, in your local <tt>~/.m2/settings.xml</tt>, you have:</p>
+<p>Now, in your local <tt>${user.home}/.m2/settings.xml</tt>, you have:</p>
<div class="source"><pre class="prettyprint linenums"><settings>
...
<profiles>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-encryption.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-encryption.html
(original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-encryption.html Thu
May 12 22:17:00 2016
@@ -459,7 +459,7 @@ Robert Scholte" />
<li><tt>settings.xml</tt> is shared between users</li></ul>
<p>The implemented solution adds the following capabilities:</p>
<ul>
-<li>authorized users have an additional <tt>settings-security.xml</tt> file in
their <tt>~/.m2</tt> folder
+<li>authorized users have an additional <tt>settings-security.xml</tt> file in
their <tt>${user.home}/.m2</tt> folder
<ul>
<li>this file either contains encrypted <b>master password</b>, used to
encrypt other passwords</li>
<li>or it can contain a <b>relocation</b> - reference to another file,
possibly on removable storage</li>
@@ -474,7 +474,7 @@ Robert Scholte" />
<p><i>Note:</i> Since Maven 3.2.1 the password argument should no longer be
used (see <a href="#Tips">Tips</a> below for more information). Maven will
prompt for the password. Earlier versions of Maven will not prompt for a
password, so it must be typed on the command-line in plaintext.</p>
<p>This command will produce an encrypted version of the password, something
like</p>
<div class="source"><pre class="prettyprint
linenums">{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</pre></div>
-<p>Store this password in the <tt>~/.m2/settings-security.xml</tt>; it should
look like</p>
+<p>Store this password in the <tt>${user.home}/.m2/settings-security.xml</tt>;
it should look like</p>
<div class="source"><pre class="prettyprint linenums"><settingsSecurity>
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
</settingsSecurity></pre></div>
@@ -525,7 +525,7 @@ Robert Scholte" />
<master>{jSMOWnoPFgsHVpMvz5VrIt5kRbzGpI8u+9EF1iFQyJQ=}</master>
</settingsSecurity></pre></div>
<p>in the file <tt>/Volumes/mySecureUsb/secure/settings-security.xml</tt></p>
-<p>And then I create <tt>~/.m2/settings-security.xml</tt> with the following
content:</p>
+<p>And then I create <tt>${user.home}/.m2/settings-security.xml</tt> with the
following content:</p>
<div class="source"><pre class="prettyprint linenums"><settingsSecurity>
<relocation>/Volumes/mySecureUsb/secure/settings-security.xml</relocation>
</settingsSecurity></pre></div>
Modified:
websites/staging/maven/trunk/content/guides/mini/guide-multiple-repositories.html
==============================================================================
---
websites/staging/maven/trunk/content/guides/mini/guide-multiple-repositories.html
(original)
+++
websites/staging/maven/trunk/content/guides/mini/guide-multiple-repositories.html
Thu May 12 22:17:00 2016
@@ -462,7 +462,7 @@
</pre></div>
<p>The <tt>repositories</tt> element is inherited so you would usually specify
the repositories to use for a group of projects by defining a
<tt>repositories</tt> element at the top of your inheritance chain.</p>
<p><b>NOTE:</b> You will also get the standard set of repositories as defined
in the <a href="../introduction/introduction-to-the-pom.html#Super_POM">Super
POM</a>.</p>
-<p>The other way you can specify the use of multiple repositories by creating
a profile in your <tt>~/.m2/settings.xml</tt> file like the following:</p>
+<p>The other way you can specify the use of multiple repositories by creating
a profile in your <tt>${user.home}/.m2/settings.xml</tt> file like the
following:</p>
<div class="source"><pre class="prettyprint linenums">
<settings>
...
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 May 12 22:17:00 2016
@@ -545,7 +545,7 @@ Karl Heinz Marbaise" />
...
</plugins></pre></div>
<p>As you can see in the example above, a JDK toolchain with
<tt><version></tt> "1.5" and <tt><vendor></tt>
"sun" 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>$<a name="user.home">user.home</a>/.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><version></tt> "1.5" and
<tt><vendor></tt> "sun". 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><version></tt> "1.5" and <tt><vendor></tt>
"sun" 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 an
d will thereby use that toolchain (that would be the JDK installed at
<tt>/path/to/jdk/1.5</tt> for our example) to compile the sources.</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><version></tt> "1.5" and
<tt><vendor></tt> "sun". 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><version></tt> "1.5" and <tt><vendor></tt>
"sun" 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>
<div class="source"><pre class="prettyprint linenums"><?xml
version="1.0" encoding="UTF8"?>
<toolchains>
<!-- JDK toolchains -->
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
