...
Maven Project resources are limited we cannot cover "backward compatilibty" across two major versions. Hence, Maven 2 support is about to be removed. Below is the summary of breaking changes, that will happen in upcoming Maven 3.9.0 and 4.0.0:
Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key MNG-6965 Theorg.codehaus.plexus:plexus-utils
artifact is not anymore "auto injected" (auto provided) to plugins classpath. Maven 2 did provide this dependency from Maven Core automatically to plugins and extensions, then Maven 3.0.0-alpha-3 added this feature to ease plugins transitionJira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key MNG-3819. This is not the case anymore. Plugin developers have to prepare for this change. Backward compatible change is really simple: just declare dependency onplexus-utils
incompile
scope, if your plugin does use classes from it, but does not have it declared (or have it inprovided
scope).- If you depend on
org.apache.maven:maven-compat
(the Maven2 compatibility layer), it's really time to look for alternatives. Note: this dependency intest
scope is "acceptable" and actually required by some testing frameworks (see below). This module is not removed in 3.9.0, nor in first releases of 4.0.x, but as part of Maven 2 backward compatibility layer, is to be removed somewhere in future.
...