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 sv...@apache.org on 2018/07/21 13:23:31 UTC

svn commit: r1836407 - in /maven/website/content: guides/mini/guide-multiple-repositories.html maven-site-1.0-site.jar pom.html

Author: svn-site-role
Date: Sat Jul 21 13:23:31 2018
New Revision: 1836407

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/guides/mini/guide-multiple-repositories.html
    maven/website/content/maven-site-1.0-site.jar
    maven/website/content/pom.html

Modified: maven/website/content/guides/mini/guide-multiple-repositories.html
==============================================================================
--- maven/website/content/guides/mini/guide-multiple-repositories.html (original)
+++ maven/website/content/guides/mini/guide-multiple-repositories.html Sat Jul 21 13:23:31 2018
@@ -181,7 +181,6 @@
 ...
 </project>
 </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>${user.home}/.m2/settings.xml</tt> file like the following:</p>
 <div class="source"><pre class="prettyprint linenums">

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

Modified: maven/website/content/pom.html
==============================================================================
--- maven/website/content/pom.html (original)
+++ maven/website/content/pom.html Sat Jul 21 13:23:31 2018
@@ -983,7 +983,7 @@ Display parameters as parsed by Maven (i
     ...
   &lt;/build&gt;
 &lt;/project&gt;</pre></div>
-<p>If the values of a <tt>*Directory</tt> element above is set as an absolute path (when their properties are expanded) then that directory is used. Otherwise, it is relative to the base build directory: <tt>${basedir}</tt>.</p></div>
+<p>If the values of a <tt>*Directory</tt> element above is set as an absolute path (when their properties are expanded) then that directory is used. Otherwise, it is relative to the base build directory: <tt>${basedir}</tt>. Please note that the <tt>scriptSourceDirectory</tt> is nowhere used in Maven and is obsolete.</p></div>
 <div class="section">
 <h5><a name="Extensions">Extensions</a></h5>
 <p>Extensions are a list of artifacts that are to be used in this build. They will be included in the running build's classpath. They can enable extensions to the build process (such as add an ftp provider for the Wagon transport mechanism), as well as make plugins active which make changes to the build lifecycle. In short, extensions are artifacts that activated during build. The extensions do not have to actually do anything nor contain a Mojo. For this reason, extensions are excellent for specifying one out of multiple implementations of a common plugin interface.</p>