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 2018/03/13 17:54:48 UTC
svn commit: r1026708 - in /websites/staging/maven/trunk/content: ./
developers/ guides/development/ guides/mini/ plugin-developers/
Author: buildbot
Date: Tue Mar 13 17:54:48 2018
New Revision: 1026708
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html
websites/staging/maven/trunk/content/guides/development/guide-testing-development-plugins.html
websites/staging/maven/trunk/content/guides/mini/guide-maven-classloading.html
websites/staging/maven/trunk/content/guides/mini/guide-using-modello.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
websites/staging/maven/trunk/content/plugin-developers/common-bugs.html
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar 13 17:54:48 2018
@@ -1 +1 @@
-1826607
+1826660
Modified: websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html (original)
+++ websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html Tue Mar 13 17:54:48 2018
@@ -129,7 +129,7 @@
<ol style="list-style-type: upper-alpha">
<li>Move to our retired area in svn</li>
<li>Move to another Apache project</li>
-<li>Move to mojo.codehaus.org, apache-extras.org or another forge</li></ol>
+<li>Move to www.mojohaus.org, apache-extras.org or another forge</li></ol>
<p>Here's a template for scenario A that can be used for the vote email:</p>
<div class="source"><pre class="prettyprint linenums">To: "Maven Developers List" <dev@maven.apache.org>
Cc: "Maven Users List" <users@maven.apache.org>
@@ -140,7 +140,7 @@ Hi,
A paragraph giving the reasons why the plugin should be retired. Make a note of
how long it has been since the latest release.
-I therefor propose that we retire maven-foo-plugin.
+I therefore propose that we retire maven-foo-plugin.
If this vote is successful I will make one final release of the plugin, making
it clear on the plugin site that it has been retired. After that the source code
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 Tue Mar 13 17:54:48 2018
@@ -131,7 +131,7 @@
<h3><a name="How_do_I_do_this.3F"></a>How do I do this?</h3>
<p>Development versions of Maven plugins are periodically published to the repository: <a class="externalLink" href="http://repository.apache.org/snapshots/">http://repository.apache.org/snapshots/</a>.</p>
<p><i>Note:</i> Currently, this is not done automatically by our continuous integration setup. This is coming soon.</p>
-<p>Other sites may publish there own - for example, the Mojo project hosts theirs at <a class="externalLink" href="http://snapshots.repository.codehaus.org/">http://snapshots.repository.codehaus.org/</a></p>
+<p>Other sites may publish there own - for example, the MojoHaus project hosts theirs at <a class="externalLink" href="https://oss.sonatype.org/content/repositories/snapshots/">https://oss.sonatype.org/content/repositories/snapshots/</a></p>
<p>The first step is to include this in your project:</p>
<div>
<pre><project>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-maven-classloading.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-maven-classloading.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-maven-classloading.html Tue Mar 13 17:54:48 2018
@@ -173,7 +173,7 @@ Anders Kristian Andersen" />
<li>Custom Classloaders</li></ul></div>
<div class="section">
<h3><a name="a1._System_Classloader"></a>1. <a name="System_Classloader">System Classloader</a></h3>
-<p>Maven uses the <a class="externalLink" href="http://classworlds.codehaus.org">Classworlds</a> classloading framework with which we create our classloader graph. If you look in your <tt>${maven.home}/boot</tt> directory you will see a single JAR which is the Classworlds JAR we use to boot the classloader graph. The Classworlds JAR is the only element of the Java <tt>CLASSPATH</tt> and Classworlds then builds the other classloaders or realms in Classworlds terminology.</p>
+<p>Maven uses the <a class="externalLink" href="https://codehaus-plexus.github.io/plexus-classworlds/">Plexus Classworlds</a> classloading framework with which we create our classloader graph. If you look in your <tt>${maven.home}/boot</tt> directory you will see a single JAR which is the Classworlds JAR we use to boot the classloader graph. The Classworlds JAR is the only element of the Java <tt>CLASSPATH</tt> and Classworlds then builds the other classloaders or realms in Classworlds terminology.</p>
<p>An Ant script like this will show the contents of the system classloader:</p>
<div>
<pre> <target name="info">
@@ -182,12 +182,12 @@ Anders Kristian Andersen" />
<div class="section">
<h3><a name="a2._Core_Classloader"></a>2. <a name="Core_Classloader">Core Classloader</a></h3>
<p>The second classloader down the graph contains the core requirements of Maven. More precisely, the core classloader has the libraries in <tt>${maven.home}/lib</tt>. In general these are just Maven libraries, e.g. instances of</p>
-<p><tt><a class="externalLink" href="http://maven.apache.org/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></tt> belong to this classloader. We hope to further separate these in the future to just be Maven APIs and have the implementations selected at runtime as required by the system.</p>
-<p>You can add elements to this classloader by <a class="externalLink" href="http://maven.apache.org/ref/current/maven-model/maven.html#class_extension">extensions</a>. These are loaded into the same place as <tt>${maven.home}/lib</tt> and hence are available to the Maven core and all plugins for the current project and subsequent projects (in future, we plan to remove it from subsequent projects).</p></div>
+<p><tt><a href="/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></tt> belong to this classloader. We hope to further separate these in the future to just be Maven APIs and have the implementations selected at runtime as required by the system.</p>
+<p>You can add elements to this classloader by <a href="/ref/current/maven-model/maven.html#class_extension">extensions</a>. These are loaded into the same place as <tt>${maven.home}/lib</tt> and hence are available to the Maven core and all plugins for the current project and subsequent projects (in future, we plan to remove it from subsequent projects).</p></div>
<div class="section">
<h3><a name="a3._Plugin_Classloaders"></a>3. <a name="Plugin_Classloaders">Plugin Classloaders</a></h3>
<p>After that, each plugin has its own classloader that is a child of Maven's core classloader. The classes in this classloader are taken from the dependencies in the plugin's dependency list.</p>
-<p>Users can add dependencies to this classloader by adding dependencies to a plugin in the <tt><a class="externalLink" href="http://maven.apache.org/ref/current/maven-model/maven.html#class_plugin">plugins/plugin</a></tt> section of their project <tt>pom.xml</tt>. Here is a sample of adding <tt>ant-nodeps</tt> to the plugin classloader of the Antrun Plugin and hereby enabling the use of additional/optional Ant tasks:</p>
+<p>Users can add dependencies to this classloader by adding dependencies to a plugin in the <tt><a href="/ref/current/maven-model/maven.html#class_plugin">plugins/plugin</a></tt> section of their project <tt>pom.xml</tt>. Here is a sample of adding <tt>ant-nodeps</tt> to the plugin classloader of the Antrun Plugin and hereby enabling the use of additional/optional Ant tasks:</p>
<div>
<pre> <plugin>
<groupId>org.apache.maven.plugins</groupId>
@@ -202,8 +202,8 @@ Anders Kristian Andersen" />
</dependencies>
...
</plugin></pre></div>
-<p>Plugins can inspect their effective runtime class path via the expressions <tt>${plugin.artifacts}</tt> or <tt>${plugin.artifactMap}</tt> to have a list or map, respectively, of resolved artifacts injected from the <tt><a class="externalLink" href="http://maven.apache.org/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/PluginDescriptor.html">PluginDescriptor</a></tt>.</p>
-<p>Please note that the plugin classloader does neither contain the <a class="externalLink" href="http://maven.apache.org/ref/current/maven-model/maven.html#class_dependency">dependencies</a> of the current project nor its build output. Instead, plugins can query the project's compile, runtime and test class path from the <tt><a class="externalLink" href="http://maven.apache.org/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></tt> in combination with the mojo annotation <tt>requiresDependencyResolution</tt> from the <a class="externalLink" href="http://maven.apache.org/developers/mojo-api-specification.html">Mojo API Specification</a>. For instance, flagging a mojo with <tt>@requiresDependencyResolution runtime</tt> enables it to query the runtime class path of the current project from which it could create further classloaders.</p>
+<p>Plugins can inspect their effective runtime class path via the expressions <tt>${plugin.artifacts}</tt> or <tt>${plugin.artifactMap}</tt> to have a list or map, respectively, of resolved artifacts injected from the <tt><a href="/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/descriptor/PluginDescriptor.html">PluginDescriptor</a></tt>.</p>
+<p>Please note that the plugin classloader does neither contain the <a href="/ref/current/maven-model/maven.html#class_dependency">dependencies</a> of the current project nor its build output. Instead, plugins can query the project's compile, runtime and test class path from the <tt><a href="/ref/current/apidocs/org/apache/maven/project/MavenProject.html">MavenProject</a></tt> in combination with the mojo annotation <tt>requiresDependencyResolution</tt> from the <a href="/developers/mojo-api-specification.html">Mojo API Specification</a>. For instance, flagging a mojo with <tt>@requiresDependencyResolution runtime</tt> enables it to query the runtime class path of the current project from which it could create further classloaders.</p>
<p>When a build plugin is executed, the thread's context classloader is set to the plugin classloader.</p></div>
<div class="section">
<h3><a name="a4._Custom_Classloaders"></a>4. <a name="Custom_Classloaders">Custom Classloaders</a></h3>
Modified: websites/staging/maven/trunk/content/guides/mini/guide-using-modello.html
==============================================================================
--- websites/staging/maven/trunk/content/guides/mini/guide-using-modello.html (original)
+++ websites/staging/maven/trunk/content/guides/mini/guide-using-modello.html Tue Mar 13 17:54:48 2018
@@ -171,8 +171,8 @@ Hervé Boutemy" />
<li>Model documentation</li>
<li>XSD</li></ul>
<p>A typical modello model looks like the following:</p>
-<div class="source"><pre class="prettyprint linenums"><model xmlns="http://codehaus-plexus.github.io/MODELLO/1.8.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://codehaus-plexus.github.io/MODELLO/1.8.0 http://codehaus-plexus.github.io/modello/xsd/modello-1.8.0.xsd"
+<div class="source"><pre class="prettyprint linenums"><model xmlns="https://codehaus-plexus.github.io/MODELLO/1.8.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="https://codehaus-plexus.github.io/MODELLO/1.8.0 https://codehaus-plexus.github.io/modello/xsd/modello-1.8.0.xsd"
xml.namespace="https://maven.apache.org/plugins/maven-archetype-plugin/archetype-descriptor/${version}"
xml.schemaLocation="http://maven.apache.org/xsd/archetype-descriptor-${version}.xsd">
<id>archetype-descriptor</id>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
Modified: websites/staging/maven/trunk/content/plugin-developers/common-bugs.html
==============================================================================
--- websites/staging/maven/trunk/content/plugin-developers/common-bugs.html (original)
+++ websites/staging/maven/trunk/content/plugin-developers/common-bugs.html Tue Mar 13 17:54:48 2018
@@ -156,7 +156,7 @@ Reader reader = new FileReader( javaFile
<p>Instead, the classes <tt>OutputStreamWriter</tt> and <tt>OutputStreamReader</tt> can be used in combination with an explicit encoding value. This encoding value can be retrieved from a mojo parameter such that the user can configure the plugin to fit his/her needs.</p>
<p>To save the user from configuring each plugin individually, conventions have been established that allow a user to centrally configure the file encoding per POM. Plugin developers should respect these conventions whereever possible:</p>
<ul>
-<li><a class="externalLink" href="http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding">Source File Encoding</a></li>
+<li><a class="externalLink" href="https://cwiki.apache.org/confluence/display/MAVEN/POM+Element+for+Source+File+Encoding">Source File Encoding</a></li>
<li><a class="externalLink" href="http://cwiki.apache.org/confluence/display/MAVENOLD/Reporting+Encoding+Configuration">Report Output Encoding</a></li></ul>
<p>Finally note that XML files require special handling because they are equipped with an encoding declaration in the XML prolog. Reading or writing XML files with an encoding that does not match their XML prolog's <tt>encoding</tt> attribute is a bad idea:</p>
<div class="source"><pre class="prettyprint linenums">/*