Author: svn-site-role
Date: Wed Nov  4 12:43:47 2026
New Revision: 1940023

Log:
d78c9c4 Say that only a flattened consumer POM drops build and properties

Modified:
   maven/website/content/whatsnewinmaven4.html

Modified: maven/website/content/whatsnewinmaven4.html
==============================================================================
--- maven/website/content/whatsnewinmaven4.html Wed Nov  4 12:20:49 2026        
(r1940022)
+++ maven/website/content/whatsnewinmaven4.html Wed Nov  4 12:43:47 2026        
(r1940023)
@@ -231,12 +231,13 @@
 <p><strong>Important note</strong>: Java 17 is only needed to <strong>run 
Maven</strong>! You can still compile against older Java versions using the 
same <a href="https://maven.apache.org/guides/mini/guide-java-target.html"; 
class="externalLink">compiler plugin configuration</a> as before. If you need 
to compile against or use another JDK, see the <a 
href="https://maven.apache.org/guides/mini/guide-using-toolchains.html"; 
class="externalLink">Guide to Using Toolchains</a> (or the article <a 
href="https://maarten.mulders.it/2021/03/introduction-to-maven-toolchains/"; 
class="externalLink">Introduction to Maven Toolchains</a> by Maven maintainer 
Maarten Mulders).</p></section><section><a id="POM_Changes"></a>
 <h2>POM Changes</h2><section><a id="Consumer_POM"></a>
 <h3>Consumer POM</h3>
-<p>Maven 4 generates a consumer POM that removes build information not needed 
by consumers (such as plugin configuration and properties), and deploys it as 
the project's POM (<code>&lt;artifactId&gt;-&lt;version&gt;.pom</code>). The 
full <code>pom.xml</code> used to build the project is deployed next to it as 
<code>&lt;artifactId&gt;-&lt;version&gt;-build.pom</code> (classifier 
<code>build</code>); with Maven 4.0.0-rc-7 this happens whether or not 
flattening is enabled.</p>
-<p>By default, the consumer POM preserves all dependencies from the build POM, 
including <code>provided</code> scope dependencies. Only build-time-only 
elements are stripped. It also keeps the <code>&lt;parent&gt;</code> reference, 
so consumers still resolve the parent POM, and the consumer POM of a parent 
(packaging <code>pom</code>) keeps its <code>&lt;build&gt;</code> and 
<code>&lt;properties&gt;</code>, which its subprojects inherit.</p>
+<p>Maven 4 generates a consumer POM and deploys it as the project's POM 
(<code>&lt;artifactId&gt;-&lt;version&gt;.pom</code>). The full 
<code>pom.xml</code> used to build the project is deployed next to it as 
<code>&lt;artifactId&gt;-&lt;version&gt;-build.pom</code> (classifier 
<code>build</code>); with Maven 4.0.0-rc-7 this happens whether or not 
flattening is enabled.</p>
+<p>By default, the consumer POM preserves all dependencies from the build POM, 
including <code>provided</code> scope dependencies. With Maven 4.0.0-rc-7 it 
also keeps the <code>&lt;parent&gt;</code> reference, 
<code>&lt;properties&gt;</code> and <code>&lt;build&gt;</code>, including 
plugin configuration. Consumers still resolve the parent POM, and the 
subprojects of a parent (packaging <code>pom</code>) still inherit its 
<code>&lt;build&gt;</code> and <code>&lt;properties&gt;</code>.</p>
 <p>Enable flattening to produce a fully self-contained consumer POM. When 
flattening is enabled:</p>
 <ul>
 
 <li>Parent POM references are resolved; all inherited elements are included 
directly</li>
+<li>Build information such as <code>&lt;build&gt;</code> and 
<code>&lt;properties&gt;</code> is removed</li>
 <li>BOM imports are flattened into the dependency list</li>
 <li>Transitive dependencies are kept (<code>compile</code> and 
<code>runtime</code> scopes). Non-transitive scopes are stripped 
(<code>provided</code>, <code>test</code>, <code>system</code> scopes)</li>
 <li>Managed dependencies are kept only if they are actually used by the 
project</li>

Reply via email to