Skip to content

Commit 968ae47

Browse files
authored
[MNGSITE-393] remove old section on plexus-utils (#156)
@eolivelli
1 parent 8e8e8dc commit 968ae47

File tree

1 file changed

+0
-29
lines changed

1 file changed

+0
-29
lines changed

content/apt/plugin-developers/common-bugs.apt

Lines changed: 0 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -456,33 +456,4 @@ public MyMojo extends AbstractMojo
456456
format for its output and also outputs debug messages even if Maven's debug mode was not enabled. For this reason,
457457
developers must not try to cache the logger during construction time. The method <<<getLog()>>> is fast enough and
458458
can simply be called whenever one needs it.
459-
460-
* {Depending on Plexus Utilities 1.1+}
461-
462-
Up to Maven 2.0.5, version 1.1 of the artifact <<<plexus-utils>>> was included in the Maven core class loader which
463-
is shared with the plugin class realm. This effectively prevented plugins from using another/newer version of
464-
<<<plexus-utils>>>. This has been solved starting with Maven 2.0.6 by shading (most of) the classes from
465-
<<<plexus-utils>>> (see {{{https://issues.apache.org/jira/browse/MNG-2892}MNG-2892}}).
466-
467-
In short, plugins that strictly require a newer version of <<<plexus-utils>>> also require Maven 2.0.6 as a minimum.
468-
Hence, a POM snippet for a Maven plugin like shown below is misleading:
469-
470-
+---
471-
<project>
472-
<packaging>maven-plugin</packaging>
473-
...
474-
<prerequisites>
475-
<!-- FIXME: This assumes the plugin works with plexus-utils:1.1, too -->
476-
<maven>2.0</maven>
477-
</prerequisites>
478-
...
479-
<dependencies>
480-
<dependency>
481-
<groupId>org.codehaus.plexus</groupId>
482-
<artifactId>plexus-utils</artifactId>
483-
<version>1.5.6</version>
484-
</dependency>
485-
</dependencies>
486-
...
487-
</project>
488459
+---

0 commit comments

Comments
 (0)