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 2016/05/12 22:08:17 UTC
svn commit: r988089 - in /websites/staging/maven/trunk/content: ./ examples/
guides/introduction/ guides/mini/
Author: buildbot
Date: Thu May 12 22:08:17 2016
New Revision: 988089
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/examples/maven-3-lifecycle-extensions.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-3rd-party-jars-remote.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
websites/staging/maven/trunk/content/settings.html
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 12 22:08:17 2016
@@ -1 +1 @@
-1743579
+1743586
Modified: websites/staging/maven/trunk/content/examples/maven-3-lifecycle-extensions.html
==============================================================================
--- websites/staging/maven/trunk/content/examples/maven-3-lifecycle-extensions.html (original)
+++ websites/staging/maven/trunk/content/examples/maven-3-lifecycle-extensions.html Thu May 12 22:08:17 2016
@@ -516,7 +516,7 @@ public class BeerMavenLifecycleParticipa
<h3><a name="Use_your_extension_in_your_builds"></a>Use your extension in your build(s)</h3>
<p>You have two ways to use your extension within your builds:</p>
<ul>
-<li>add your extension jar in $M2_HOME/lib/ext.</li>
+<li>add your extension jar in <tt>${maven.home}/lib/ext</tt>.</li>
<li>add it as a build extension in your pom.</li></ul>
<p><b>NOTE</b>: if you use a build extension mechanism the method <tt>afterSessionStart</tt> <b>won't be called</b></p>
<p>Use a extension in your project, declare as it in your pom:</p>
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:08:17 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>$M2_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>~/.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:08:17 2016
@@ -452,7 +452,7 @@
<li>Per User
<p>- Defined in the <a class="externalLink" href="http://maven.apache.org/ref/2.2.1/maven-settings/settings.html"> Maven-settings</a> <tt>(%USER_HOME%/.m2/settings.xml)</tt>.</p></li>
<li>Global
-<p>- Defined in the <a class="externalLink" href="http://maven.apache.org/ref/2.2.1/maven-settings/settings.html"> global Maven-settings</a> <tt>(%M2_HOME%/conf/settings.xml)</tt>.</p></li>
+<p>- Defined in the <a class="externalLink" href="http://maven.apache.org/ref/2.2.1/maven-settings/settings.html"> global Maven-settings</a> <tt>(${maven.home}/conf/settings.xml)</tt>.</p></li>
<li>Profile descriptor
<p>- a descriptor located in <a class="externalLink" href="http://maven.apache.org/ref/2.2.1/maven-profile/profiles.html">project basedir <tt>(profiles.xml)</tt></a> (unsupported in Maven 3.0: see <a class="externalLink" href="https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-profiles.xml"> Maven 3 compatibility notes</a>)</p></li></ul></div>
<div class="section">
Modified: websites/staging/maven/trunk/content/guides/mini/guide-3rd-party-jars-remote.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-3rd-party-jars-remote.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-3rd-party-jars-remote.html Thu May 12 22:08:17 2016
@@ -443,7 +443,7 @@
<h2><a name="Guide_to_deploying_3rd_party_JARs_to_remote_repository"></a>Guide to deploying 3rd party JARs to remote repository</h2>
<p>Same concept of the <a href="./guide-3rd-party-jars-local.html">install:install-file</a> goal of the maven-install-plugin where the 3rd party JAR is installed in the local repository. But this time instead to local repository the JAR will be install both in the local and remote repository.</p>
<p>To deploy a 3rd party JAR use the deploy:deploy-file goal under maven-deploy-plugin.</p>
-<p>First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to your %M2_HOME%/lib.</p>
+<p>First, the wagon-provider(wagon-ftp, wagon-file, etc..) must be placed to your <tt>${maven.home}/lib</tt>.</p>
<p>Then execute the command:</p>
<div class="source"><pre class="prettyprint linenums">mvn deploy:deploy-file -DgroupId=<group-id> \
-DartifactId=<artifact-id> \
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: websites/staging/maven/trunk/content/settings.html
==============================================================================
--- websites/staging/maven/trunk/content/settings.html (original)
+++ websites/staging/maven/trunk/content/settings.html Thu May 12 22:08:17 2016
@@ -534,7 +534,7 @@
<ul>
-<li>The Maven install: <tt>$M2_HOME/conf/settings.xml</tt></li>
+<li>The Maven install: <tt>${maven.home}/conf/settings.xml</tt></li>
<li>A user’s install: <tt>${user.home}/.m2/settings.xml</tt></li>
</ul>