Author: svn-site-role
Date: Thu Jun 26 08:48:11 2025
New Revision: 1926736
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/docs/4.0.0-rc-4/release-notes.html
Modified: maven/website/content/docs/4.0.0-rc-4/release-notes.html
==============================================================================
--- maven/website/content/docs/4.0.0-rc-4/release-notes.html (original)
+++ maven/website/content/docs/4.0.0-rc-4/release-notes.html Thu Jun 26
08:48:11 2025
@@ -171,18 +171,24 @@ Please refer to the <a href="https://mav
<li>This is a release candidate version intended for testing and feedback</li>
<li>Please report any issues to GitHub: <a
href="https://github.com/apache/maven/issues";
class="externalLink">https://github.com/apache/maven/issues</a></li>
<li>For production use, consider the stability and compatibility requirements
of your project</li>
-</ul></section></section></section><section><a id="Upgrading_from_Maven_3"></a>
-<h1>Upgrading from Maven 3</h1>
-<p>Maven 4 brings a tons of changes. We've tried hard to maximise
compatibility with Maven 3.x, but in order to have your build work with Maven
4, you will need to upgrade some plugins (such as
<code>maven-enforcer-plugin</code>, <code>maven-remote-resources-plugin</code>,
<code>maven-shade-plugin</code>, etc…) to their most recent versions.</p>
-<p>A lot of deprecated constructs in POM files are now rejected. If you
encounter an issue when building your project with Maven 4, first try to use
the upgrade tool using <code>mvnup check</code> to see if there's anything that
can be easily and automatically fixed, and then (or directly) <code>mvnup
apply</code> to apply those changes.</p>
-<p>If your build is leveraging Maven extensions, you may very well expect some
breakage. Some extensions may need to be updated:</p>
+</ul></section><section><a id="Upgrading_from_Maven_3"></a>
+<h3>Upgrading from Maven 3</h3>
+<p>Maven 4 introduces significant changes to enhance functionality and
performance. While we’ve prioritized compatibility with Maven 3.x, some
POM files may require updates to build successfully with Maven 4.</p>
+<p>To identify and resolve common issues, use the Maven upgrade tool:</p>
<ul>
-<li>the useful, but unmaintained, <a
href="https://github.com/trustin/os-maven-plugin/";
class="externalLink"><code>os-maven-plugin</code></a> extension has been
replaced with at <a href="https://github.com/maveniverse/nisse";
class="externalLink"><code>nisse</code></a> extension.</li>
+<li>Run <code>mvnup check</code> to detect potential problems in your
project.</li>
+<li>Run <code>mvnup apply</code> to automatically apply recommended fixes.</li>
</ul>
-<p>Contact the extensions' developers team to know their plans regarding
supporting to Maven 4.</p></section><section><a
id="Upgrading_from_Maven_4.0.0-rc-3"></a>
-<h1>Upgrading from Maven 4.0.0-rc-3</h1>
-<p>No known incompatibilities since last RC.</p><section><a id="Changelog"></a>
+<p>If your build relies on Maven extensions not supported by the upgrade tool,
contact the extension developers to confirm their plans for Maven 4
compatibility.</p>
+<p>If your build still fails, run it with the <code>-e</code> option to
generate a detailed stack trace. Then, file an issue including:</p>
+<ul>
+
+<li>The full stack trace.</li>
+<li>A link to the exact branch of your open-source project, or a minimal
reproducer for proprietary projects.</li>
+</ul></section><section><a id="Upgrading_from_Maven_4.0.0-rc-3"></a>
+<h3>Upgrading from Maven 4.0.0-rc-3</h3>
+<p>No known incompatibilities since last
RC.</p></section></section><section><a id="Changelog"></a>
<h2>Changelog</h2>
<p>Maven 4.0.0-rc-4 aims at being the last release candidate before Maven
4.0.0 GA. We'll focus on fixing critical bugs raised before GA.
Worth mentioning is the new upgrade tool which can be used to fix your
<code>pom.xml</code> files and make them usable in Maven
4.</p></section><section><a id="a.3F.3F_New_features_and_improvements"></a>
