svn commit: r1876570 - in /maven/website/content: maven-site-1.0-site.jar plugin-developers/common-bugs.html

[sv...@apache.org]

Author: svn-site-role
Date: Wed Apr 15 20:43:43 2020
New Revision: 1876570

Log:
Site checkin for project Apache Maven Site

Modified:
    maven/website/content/maven-site-1.0-site.jar
    maven/website/content/plugin-developers/common-bugs.html

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

Modified: maven/website/content/plugin-developers/common-bugs.html
==============================================================================
--- maven/website/content/plugin-developers/common-bugs.html (original)
+++ maven/website/content/plugin-developers/common-bugs.html Wed Apr 15 20:43:43 2020
@@ -329,27 +329,7 @@ if ( !file.isAbsolute() )
         log.debug( "..." );
     }
 }</pre></div>
-<p>In case of the logger, the above mojo will simply use a default console logger, i.e. the code defect is not immediately noticeable by a <code>NullPointerException</code>. This default logger will however use a different message format for its output and also outputs debug messages even if Maven's debug mode was not enabled. For this reason, developers must not try to cache the logger during construction time. The method <code>getLog()</code> is fast enough and can simply be called whenever one needs it.</p></section><section>
-<h3><a name="Depending_on_Plexus_Utilities_1.1.2B"></a><a name="Depending_on_Plexus_Utilities_1.1">Depending on Plexus Utilities 1.1+</a></h3>
-<p>Up to Maven 2.0.5, version 1.1 of the artifact <code>plexus-utils</code> was included in the Maven core class loader which is shared with the plugin class realm. This effectively prevented plugins from using another/newer version of <code>plexus-utils</code>. This has been solved starting with Maven 2.0.6 by shading (most of) the classes from <code>plexus-utils</code> (see <a class="externalLink" href="https://issues.apache.org/jira/browse/MNG-2892">MNG-2892</a>).</p>
-<p>In short, plugins that strictly require a newer version of <code>plexus-utils</code> also require Maven 2.0.6 as a minimum. Hence, a POM snippet for a Maven plugin like shown below is misleading:</p>
-<div class="source"><pre class="prettyprint linenums">&lt;project&gt;
-  &lt;packaging&gt;maven-plugin&lt;/packaging&gt;
-  ...
-  &lt;prerequisites&gt;
-    &lt;!-- FIXME: This assumes the plugin works with plexus-utils:1.1, too --&gt;
-    &lt;maven&gt;2.0&lt;/maven&gt;
-  &lt;/prerequisites&gt;
-  ...
-  &lt;dependencies&gt;
-    &lt;dependency&gt;
-      &lt;groupId&gt;org.codehaus.plexus&lt;/groupId&gt;
-      &lt;artifactId&gt;plexus-utils&lt;/artifactId&gt;
-      &lt;version&gt;1.5.6&lt;/version&gt;
-    &lt;/dependency&gt;
-  &lt;/dependencies&gt;
-  ...
-&lt;/project&gt;</pre></div></section></section>
+<p>In case of the logger, the above mojo will simply use a default console logger, i.e. the code defect is not immediately noticeable by a <code>NullPointerException</code>. This default logger will however use a different message format for its output and also outputs debug messages even if Maven's debug mode was not enabled. For this reason, developers must not try to cache the logger during construction time. The method <code>getLog()</code> is fast enough and can simply be called whenever one needs it. +---</p></section></section>
         </main>
       </div>
     </div>