You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-commits@maven.apache.org by sv...@apache.org on 2024/12/22 22:11:45 UTC
svn commit: r1922640 - in /maven/website/content: docs/3.5.0-beta-1/release-notes.html docs/3.5.0/release-notes.html maven-ci-friendly.html
Author: svn-site-role
Date: Sun Dec 22 22:11:45 2024
New Revision: 1922640
Log:
Site checkin for project Apache Maven Site
Modified:
maven/website/content/docs/3.5.0-beta-1/release-notes.html
maven/website/content/docs/3.5.0/release-notes.html
maven/website/content/maven-ci-friendly.html
Modified: maven/website/content/docs/3.5.0-beta-1/release-notes.html
==============================================================================
--- maven/website/content/docs/3.5.0-beta-1/release-notes.html (original)
+++ maven/website/content/docs/3.5.0-beta-1/release-notes.html Sun Dec 22 22:11:45 2024
@@ -171,20 +171,30 @@ See the <a href="../../plugins/index.htm
<li>the reference documentation: <a href="/ref/3.5.0-beta-1/">http://maven.apache.org/ref/3.5.0-beta-1/</a></li>
</ul><section><a id="Known_Issues"></a>
<h2>Known Issues</h2>
-<p>The following issues were identified during release testing of this <em>BETA</em> release but have not been deemed as release blockers:</p>
+<p>The following issues were identified during release testing of this <em>BETA</em> release but have not been deemed as release
+blockers:</p>
<ul>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6190" class="externalLink">MNG-6190</a> maven-resolver-provider's <code>DefaultArtifactDescriptorReader</code> has mismatched constructor and initService methods (this issue does not affect normal usage of Maven)</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-6190" class="externalLink">MNG-6190</a> maven-resolver-provider's <code>DefaultArtifactDescriptorReader</code> has mismatched constructor and initService
+methods (this issue does not affect normal usage of Maven)</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6191" class="externalLink">MNG-6191</a> <code>mvn -f</code> complains about illegal <code>readlink</code> option under macOS</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6192" class="externalLink">MNG-6192</a> The distribution zip file has unordered entries and some tools - most notably Maven wrapper - will fail to unzip the distribution</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-6192" class="externalLink">MNG-6192</a> The distribution zip file has unordered entries and some tools - most notably Maven wrapper - will fail to
+unzip the distribution</li>
</ul></section><section><a id="Why_not_Maven_3.4.0.3F"></a>
<h2>Why not Maven 3.4.0?</h2>
-<p>After Maven 3.3.9 was released, the Eclipse Aether project was retired and the code base was migrated to the Apache Maven project.</p>
-<p>The original goal for the 3.4.0 release was to replace Aether with the exact same code after migration to the Apache Maven project and then proceed with bug fixes to the resolver code as well as other areas of Maven.</p>
-<p>The migration of the code between the two foundations took longer than expected and as a result there were other changes committed to Maven core that were outside the scope of intent for 3.4.0.</p>
-<p>In order to refocus on the original intent for 3.4.0, the decision was taken to revert the Maven core history to the point of the 3.3.9 release and merge in the desired changes one at a time.</p>
-<p>Because there had been a lot of communication about different features being delivered and bugs fixed in Maven 3.4.0 and the new history may not contain them in the first release, the decision was taken to forever burn the 3.4.x release line.</p>
-<p>More detail on this decision can be read in the <a href="http://www.mail-archive.com/dev@maven.apache.org/msg112103.html" class="externalLink">mailing list archive</a>.</p></section><section><a id="Reporters_and_Contributors_of_this_release"></a>
+<p>After Maven 3.3.9 was released, the Eclipse Aether project was retired and the code base was migrated to the Apache
+Maven project.</p>
+<p>The original goal for the 3.4.0 release was to replace Aether with the exact same code after migration to the Apache
+Maven project and then proceed with bug fixes to the resolver code as well as other areas of Maven.</p>
+<p>The migration of the code between the two foundations took longer than expected and as a result there were other changes
+committed to Maven core that were outside the scope of intent for 3.4.0.</p>
+<p>In order to refocus on the original intent for 3.4.0, the decision was taken to revert the Maven core history to the
+point of the 3.3.9 release and merge in the desired changes one at a time.</p>
+<p>Because there had been a lot of communication about different features being delivered and bugs fixed in Maven 3.4.0 and
+the new history may not contain them in the first release, the decision was taken to forever burn the 3.4.x release
+line.</p>
+<p>More detail on this decision can be read in
+the <a href="http://www.mail-archive.com/dev@maven.apache.org/msg112103.html" class="externalLink">mailing list archive</a>.</p></section><section><a id="Reporters_and_Contributors_of_this_release"></a>
<h2>Reporters and Contributors of this release</h2>
<p>Bugs:</p>
<ul>
@@ -263,13 +273,15 @@ or <code>mvn deploy</code> more details
<p>Bugs:</p>
<ul>
-<li><a href="https://issues.apache.org/jira/browse/MNG-5895" class="externalLink">MNG-5895</a> - Problem with CI friendly usage of ${..} which is already defined via property in pom file.</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6057" class="externalLink">MNG-6057</a> - Problem with CI friendly usage of ${..} reactor order is changed</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-5895" class="externalLink">MNG-5895</a> - Problem with CI friendly usage of <code>${..}</code> which is already defined via property in pom file.</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-6057" class="externalLink">MNG-6057</a> - Problem with CI friendly usage of <code>${..}</code> reactor order is changed</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6090" class="externalLink">MNG-6090</a> - CI friendly properties break submodule builds</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6170" class="externalLink">MNG-6170</a> - NPE in cases using Multithreaded -T X versions:set -DnewVersion=1.0-SNAPSHOT</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6173" class="externalLink">MNG-6173</a> - MavenSession.getAllProjects() should return all projects in the reactor</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6176" class="externalLink">MNG-6176</a> - Javadoc errors prevent release with Java 8</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6177" class="externalLink">MNG-6177</a> - The –file command line option of the Windows and Unix launchers does not work for directory names like “Spaces & Special Char”</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-6177" class="externalLink">MNG-6177</a> - The <code>--file</code> command line option of the Windows and Unix launchers does not work for directory names
+like "
+Spaces & Special Char"</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6180" class="externalLink">MNG-6180</a> - groupId has plain color when goal fails</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6181" class="externalLink">MNG-6181</a> - HttpClient produces a lot of noise at debug loglevel</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6183" class="externalLink">MNG-6183</a> - Dependency management debug message corrections.</li>
Modified: maven/website/content/docs/3.5.0/release-notes.html
==============================================================================
--- maven/website/content/docs/3.5.0/release-notes.html (original)
+++ maven/website/content/docs/3.5.0/release-notes.html Sun Dec 22 22:11:45 2024
@@ -149,8 +149,10 @@
<h1>Release Notes – Maven 3.5.0</h1>
<p>The Apache Maven team would like to announce the release of Maven 3.5.0.</p>
<p>Maven 3.5.0 is <a href="../../download.html">available for download</a>.</p>
-<p>Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central place.</p>
-<p>The core release is independent of the plugins available. Further releases of plugins will be made separately. See the <a href="../../plugins/index.html">PluginList</a> for more information.</p>
+<p>Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM),
+Maven can manage a project's build, reporting and documentation from a central place.</p>
+<p>The core release is independent of the plugins available. Further releases of plugins will be made separately. See
+the <a href="../../plugins/index.html">PluginList</a> for more information.</p>
<p>We hope you enjoy using Maven! If you have any questions, please consult:</p>
<ul>
@@ -159,11 +161,17 @@
<li>the reference documentation: <a href="/ref/3.5.0/">http://maven.apache.org/ref/3.5.0/</a></li>
</ul><section><a id="Why_not_Maven_3.4.0.3F"></a>
<h2>Why not Maven 3.4.0?</h2>
-<p>After Maven 3.3.9 was released, the Eclipse Aether project was retired and the code base was migrated to the Apache Maven project.</p>
-<p>The original goal for the 3.4.0 release was to replace Aether with the exact same code after migration to the Apache Maven project and then proceed with bug fixes to the resolver code as well as other areas of Maven.</p>
-<p>The migration of the code between the two foundations took longer than expected and as a result there were other changes committed to Maven core that were outside the scope of intent for 3.4.0.</p>
-<p>In order to refocus on the original intent for 3.4.0, the decision was taken to revert the Maven core history to the point of the 3.3.9 release and merge in the desired changes one at a time.</p>
-<p>Because there had been a lot of communication about different features being delivered and bugs fixed in Maven 3.4.0 and the new history may not contain them in the first release, the decision was taken to forever burn the 3.4.x release line.</p>
+<p>After Maven 3.3.9 was released, the Eclipse Aether project was retired and the code base was migrated to the Apache
+Maven project.</p>
+<p>The original goal for the 3.4.0 release was to replace Aether with the exact same code after migration to the Apache
+Maven project and then proceed with bug fixes to the resolver code as well as other areas of Maven.</p>
+<p>The migration of the code between the two foundations took longer than expected and as a result there were other changes
+committed to Maven core that were outside the scope of intent for 3.4.0.</p>
+<p>In order to refocus on the original intent for 3.4.0, the decision was taken to revert the Maven core history to the
+point of the 3.3.9 release and merge in the desired changes one at a time.</p>
+<p>Because there had been a lot of communication about different features being delivered and bugs fixed in Maven 3.4.0 and
+the new history may not contain them in the first release, the decision was taken to forever burn the 3.4.x release
+line.</p>
<p>More detail on this decision can be read in the <a href="http://www.mail-archive.com/dev@maven.apache.org/msg112103.html" class="externalLink">mailing list archive</a>.</p></section><section><a id="Reporters_and_Contributors_of_this_release"></a>
<h2>Reporters and Contributors of this release</h2>
<p>Bugs:</p>
@@ -211,34 +219,48 @@
<li>
<p>The most obvious change you may encounter is that the console output has colors now <a href="https://issues.apache.org/jira/browse/MNG-3507" class="externalLink">MNG-3507</a>, <a href="https://issues.apache.org/jira/browse/MNG-6093" class="externalLink">MNG-6093</a>.</p></li>
<li>
-<p>The new <code>project.directory</code> special property adds support in every calculated URLs (project, SCM, site) for module directory name that does not match artifactId <a href="https://issues.apache.org/jira/browse/MNG-5878" class="externalLink">MNG-5878</a></p></li>
+<p>The new <code>project.directory</code> special property adds support in every calculated URLs (project, SCM, site) for module
+directory name that does not match artifactId <a href="https://issues.apache.org/jira/browse/MNG-5878" class="externalLink">MNG-5878</a></p></li>
<li>
-<p>The <code>JAVA_HOME</code> discovery has been reduced to simply check if <code>JAVA_HOME</code> is set or not then trying to discover via <code>which java</code>, nothing more <a href="https://issues.apache.org/jira/browse/MNG-6003" class="externalLink">MNG-6003</a>.</p></li>
+<p>The <code>JAVA_HOME</code> discovery has been reduced to simply check if <code>JAVA_HOME</code> is set or not then trying to discover via
+<code>which java</code>, nothing more <a href="https://issues.apache.org/jira/browse/MNG-6003" class="externalLink">MNG-6003</a>.</p></li>
<li>
-<p>The build bootstrapping support via Apache Ant has been removed. You can now only bootstrap Maven build with a previous version of Maven, but not with Ant any more <a href="https://issues.apache.org/jira/browse/MNG-5904" class="externalLink">MNG-5904</a>.</p></li>
+<p>The build bootstrapping support via Apache Ant has been removed. You can now only bootstrap Maven build with a
+previous version of Maven, but not with Ant anymore <a href="https://issues.apache.org/jira/browse/MNG-5904" class="externalLink">MNG-5904</a>.</p></li>
<li>
-<p>Based on problems in using <code>M2_HOME</code> related to different Maven versions installed and to simplify things, the usage of <code>M2_HOME</code> has been removed and is not supported any more <a href="https://issues.apache.org/jira/browse/MNG-5823" class="externalLink">MNG-5823</a>, <a href="https://issues.apache.org/jira/browse/MNG-5836" class="externalLink">MNG-5836</a>, <a href="https://issues.apache.org/jira/browse/MNG-5607" class="externalLink">MNG-5607</a>.</p></li>
+<p>Based on problems in using <code>M2_HOME</code> related to different Maven versions installed and to simplify things, the usage
+of <code>M2_HOME</code> has been removed and is not supported anymore <a href="https://issues.apache.org/jira/browse/MNG-5823" class="externalLink">MNG-5823</a>, <a href="https://issues.apache.org/jira/browse/MNG-5836" class="externalLink">MNG-5836</a>, <a href="https://issues.apache.org/jira/browse/MNG-5607" class="externalLink">MNG-5607</a>.</p></li>
<li>
<p>Important change for windows users: The usage of <code>%HOME%</code> has been replaced with <code>%USERPROFILE%</code> <a href="https://issues.apache.org/jira/browse/MNG-6001" class="externalLink">MNG-6001</a></p></li>
<li>
-<p>Several issues have been reported and fixed related to the <code>mvn</code> script either for Unix/Linux/Cygwin/Solaris or for Windows <a href="https://issues.apache.org/jira/browse/MNG-5815" class="externalLink">MNG-5815</a>, <a href="https://issues.apache.org/jira/browse/MNG-5852" class="externalLink">MNG-5852</a>, <a href="https://issues.apache.org/jira/browse/MNG-5963" class="externalLink">MNG-5963</a>, <a href="https://issues.apache.org/jira/browse/MNG-6022" class="externalLink">MNG-6022</a>.</p></li>
+<p>Several issues have been reported and fixed related to the <code>mvn</code> script either for Unix/Linux/Cygwin/Solaris or for
+Windows <a href="https://issues.apache.org/jira/browse/MNG-5815" class="externalLink">MNG-5815</a>, <a href="https://issues.apache.org/jira/browse/MNG-5852" class="externalLink">MNG-5852</a>, <a href="https://issues.apache.org/jira/browse/MNG-5963" class="externalLink">MNG-5963</a>, <a href="https://issues.apache.org/jira/browse/MNG-6022" class="externalLink">MNG-6022</a>.</p></li>
<li>
-<p>In Maven 3.3.9, we have removed bindings for maven-ejb3-plugin because it does not exist. We follow-up and removed the artifact handler for <code>ejb3</code> and the <code>par</code> lifecycles <a href="https://issues.apache.org/jira/browse/MNG-6014" class="externalLink">MNG-6014</a>, <a href="https://issues.apache.org/jira/browse/MNG-6017" class="externalLink">MNG-6017</a>.</p></li>
+<p>In Maven 3.3.9, we have removed bindings for maven-ejb3-plugin because it does not exist. We follow-up and removed the
+artifact handler for <code>ejb3</code> and the <code>par</code> lifecycles <a href="https://issues.apache.org/jira/browse/MNG-6014" class="externalLink">MNG-6014</a>, <a href="https://issues.apache.org/jira/browse/MNG-6017" class="externalLink">MNG-6017</a>.</p></li>
<li>
-<p>In previous Maven versions, there had been a larger problem related to memory usage in case of very large reactors (200-300 modules or more) which caused failures with out of memory exceptions or the need to increase the memory settings. This problem has been fixed with <a href="https://issues.apache.org/jira/browse/MNG-6030" class="externalLink">MNG-6030</a>.</p></li>
+<p>In previous Maven versions, there had been a larger problem related to memory usage in case of very large reactors (
+200-300 modules or more) which caused failures with out of memory exceptions or the need to increase the memory
+settings. This problem has been fixed with <a href="https://issues.apache.org/jira/browse/MNG-6030" class="externalLink">MNG-6030</a>.</p></li>
<li>
-<p>If you have defined a property within the <code>.mvn/maven.config</code> file, it was not possible to overwrite the property via command line. This has been fixed with <a href="https://issues.apache.org/jira/browse/MNG-6078" class="externalLink">MNG-6078</a>.</p></li>
+<p>If you have defined a property within the <code>.mvn/maven.config</code> file, it was not possible to overwrite the property via
+command line. This has been fixed with <a href="https://issues.apache.org/jira/browse/MNG-6078" class="externalLink">MNG-6078</a>.</p></li>
<li>
-<p>If you have are using <code><prerequisites>..</prerequisites></code> for a non maven-plugin project, you will get a WARNING which looks like this:</p>
+<p>If you have are using <code><prerequisites>..</prerequisites></code> for a non maven-plugin project, you will get a WARNING which
+looks like this:</p>
<pre><code class="nohighlight nocode"> [INFO] Scanning for projects...
[WARNING] The project org.apache.maven:maven:pom:3.5.0 uses prerequisites which is only intended for maven-plugin projects but not for non maven-plugin projects. For such purposes you should use the maven-enforcer-plugin. See https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
</code></pre>
-<p>This will tell you to use <a href="/enforcer/maven-enforcer-plugin/">maven-enforcer-plugin</a> to check the version of Maven you are expecting to build your project with, instead of using <code>prerequisites</code> <a href="https://issues.apache.org/jira/browse/MNG-5297" class="externalLink">MNG-5297</a>, <a href="https://issues.apache.org/jira/browse/MNG-6092" class="externalLink">MNG-6092</a>.</p></li>
+<p>This will tell you to use <a href="/enforcer/maven-enforcer-plugin/">maven-enforcer-plugin</a> to check the version of Maven you are expecting to build your
+project with, instead of using <code>prerequisites</code> <a href="https://issues.apache.org/jira/browse/MNG-5297" class="externalLink">MNG-5297</a>, <a href="https://issues.apache.org/jira/browse/MNG-6092" class="externalLink">MNG-6092</a>.</p></li>
<li>
<p>Replaced Eclipse Aether with <a href="/resolver/">Maven Resolver</a> <a href="https://issues.apache.org/jira/browse/MNG-6110" class="externalLink">MNG-6110</a>, <a href="https://issues.apache.org/jira/browse/MNG-6140" class="externalLink">MNG-6140</a>.</p></li>
<li>
-<p>Using of CI friendly versions via <code>${revision}</code>, <code>${sha1}</code> and/or <code>${changelist}</code> has been fixed <a href="https://issues.apache.org/jira/browse/MNG-6057" class="externalLink">MNG-6057</a>, <a href="https://issues.apache.org/jira/browse/MNG-6090" class="externalLink">MNG-6090</a> and <a href="https://issues.apache.org/jira/browse/MNG-5895" class="externalLink">MNG-5895</a>. It is very important to know if you are using the previously named properties for a version in your pom you have to use <a href="https://www.mojohaus.org/flatten-maven-plugin/" class="externalLink">flatten-maven-plugin</a> if you like to do an <code>mvn install</code> or <code>mvn deploy</code> more details can be found at <a href="/maven-ci-friendly.html">Maven CI Friendly Versions</a>.</p></li>
+<p>Using of CI friendly versions via <code>${revision}</code>, <code>${sha1}</code> and/or <code>${changelist}</code> has been
+fixed <a href="https://issues.apache.org/jira/browse/MNG-6057" class="externalLink">MNG-6057</a>, <a href="https://issues.apache.org/jira/browse/MNG-6090" class="externalLink">MNG-6090</a> and <a href="https://issues.apache.org/jira/browse/MNG-5895" class="externalLink">MNG-5895</a>. It is very important to know if you are using the previously named
+properties for a version in your pom you have to use <a href="https://www.mojohaus.org/flatten-maven-plugin/" class="externalLink">flatten-maven-plugin</a> if you like to do an <code>mvn install</code> or
+<code>mvn deploy</code> more details can be found at <a href="/maven-ci-friendly.html">Maven CI Friendly Versions</a>.</p></li>
</ul></section><section><a id="Improvements"></a>
<h2>Improvements</h2>
<p>The full list of changes as well as detailed descriptions of same can be found in our <a href="https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12336084&styleName=Text" class="externalLink">issue management system</a>.</p><section><a id="Bugs"></a>
@@ -246,21 +268,22 @@
<ul>
<li><a href="https://issues.apache.org/jira/browse/MNG-5297" class="externalLink">MNG-5297</a> - Site should tell ‘prerequisites.maven is deprecated’</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-5368" class="externalLink">MNG-5368</a> - UnsupportedOperationException thrown when version range is not correct in dependencyManagement definitions</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-5368" class="externalLink">MNG-5368</a> - UnsupportedOperationException thrown when version range is not correct in dependencyManagement
+definitions</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5629" class="externalLink">MNG-5629</a> - ClosedChannelException from DefaultUpdateCheckManager.read</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5815" class="externalLink">MNG-5815</a> - “mvn.cmd” does not indicate failure properly when using “&&”</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5823" class="externalLink">MNG-5823</a> - mvnDebug doesn't work with <code>M2_HOME</code> with spaces - missing quotes</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5829" class="externalLink">MNG-5829</a> - mvn shell script fails with syntax error on Solaris 10</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5836" class="externalLink">MNG-5836</a> - logging config is overridden by <code>$M2_HOME/lib/ext/*.jar</code></li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5852" class="externalLink">MNG-5852</a> - mvn shell script invokes <code>/bin/sh</code> but requires Bash functions</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-5895" class="externalLink">MNG-5895</a> - Problem with CI friendly usage of `${..}`` which is already defined via property in pom file.</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-5895" class="externalLink">MNG-5895</a> - Problem with CI friendly usage of <code>${..}</code> which is already defined via property in pom file.</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5958" class="externalLink">MNG-5958</a> - <code>java.lang.String</code> cannot be cast to <code>org.apache.maven.lifecycle.mapping.LifecyclePhase</code></li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5961" class="externalLink">MNG-5961</a> - Maven possibly not aware of log4j2</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5962" class="externalLink">MNG-5962</a> - <code>mvn.cmd</code> fails when the current directory has spaces in between</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-5963" class="externalLink">MNG-5963</a> - <code>mvn.cmd</code> does not return ERROR_CODE</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6022" class="externalLink">MNG-6022</a> - <code>mvn.cmd</code> fails if directory contains an ampersand (<code>&</code>)</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6053" class="externalLink">MNG-6053</a> - Unsafe System Properties copy in <code>MavenRepositorySystemUtils</code>, causing NPEs</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6057" class="externalLink">MNG-6057</a> - Problem with CI friendly usage of `${..} reactor order is changed</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-6057" class="externalLink">MNG-6057</a> - Problem with CI friendly usage of <code>${..}</code> reactor order is changed</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6090" class="externalLink">MNG-6090</a> - CI friendly properties break submodule builds</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6105" class="externalLink">MNG-6105</a> - <code>properties.internal.SystemProperties.addSystemProperties()</code> is not really thread-safe</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6109" class="externalLink">MNG-6109</a> - <code>PluginDescriptor</code> doesn't read since value of parameter</li>
@@ -273,11 +296,13 @@
<li><a href="https://issues.apache.org/jira/browse/MNG-6172" class="externalLink">MNG-6172</a> - Precedence of command-line system property options has changed</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6173" class="externalLink">MNG-6173</a> - <code>MavenSession.getAllProjects()</code> should return all projects in the reactor</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6176" class="externalLink">MNG-6176</a> - Javadoc errors prevent release with Java 8</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6177" class="externalLink">MNG-6177</a> - The <code>--file</code> command line option of the Windows and Unix launchers does not work for directory names like “<code>Spaces & Special Char</code>”</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-6177" class="externalLink">MNG-6177</a> - The <code>--file</code> command line option of the Windows and Unix launchers does not work for directory names
+like “<code>Spaces & Special Char</code>”</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6180" class="externalLink">MNG-6180</a> - groupId has plain color when goal fails</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6181" class="externalLink">MNG-6181</a> - HttpClient produces a lot of noise at debug loglevel</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6183" class="externalLink">MNG-6183</a> - Dependency management debug message corrections.</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-6190" class="externalLink">MNG-6190</a> - maven-resolver-provider's <code>DefaultArtifactDescriptorReader</code> has mismatched constructor and initService methods</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-6190" class="externalLink">MNG-6190</a> - maven-resolver-provider's <code>DefaultArtifactDescriptorReader</code> has mismatched constructor and initService
+methods</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6191" class="externalLink">MNG-6191</a> - <code>mvn -f</code> complains about illegal <code>readlink</code> option under macOS</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6192" class="externalLink">MNG-6192</a> - distribution zip file has unordered entries</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6195" class="externalLink">MNG-6195</a> - Use consistent quoting forms in <code>mvn</code> launcher script</li>
@@ -329,7 +354,8 @@
<ul>
<li><a href="https://issues.apache.org/jira/browse/MNG-3507" class="externalLink">MNG-3507</a> - ANSI color logging for improved output visibility</li>
-<li><a href="https://issues.apache.org/jira/browse/MNG-5878" class="externalLink">MNG-5878</a> - add support for module name != <code>artifactId</code> in every calculated URLs (project, SCM, site): special <code>project.directory</code> property</li>
+<li><a href="https://issues.apache.org/jira/browse/MNG-5878" class="externalLink">MNG-5878</a> - add support for module name != <code>artifactId</code> in every calculated URLs (project, SCM, site): special
+<code>project.directory</code> property</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6093" class="externalLink">MNG-6093</a> - create a <code>slf4j-simple</code> provider extension that supports level color rendering</li>
<li><a href="https://issues.apache.org/jira/browse/MNG-6182" class="externalLink">MNG-6182</a> - ModelResolver interface enhancement: addition of <code>resolveModel(Dependency)</code> supporting version ranges</li>
</ul></section><section><a id="Tasks"></a>
Modified: maven/website/content/maven-ci-friendly.html
==============================================================================
--- maven/website/content/maven-ci-friendly.html (original)
+++ maven/website/content/maven-ci-friendly.html Sun Dec 22 22:11:45 2024
@@ -149,7 +149,8 @@ and/or <code>${changelist}</code> as pla
<h2>Single Project Setup</h2>
<p>This can look like this:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -178,7 +179,8 @@ line like this:</p>
<p>This will become cumbersome over the time. So the other solution for this is
to simply use a property inside the pom file which looks like this:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -200,12 +202,13 @@ to simply use a property inside the pom
<pre><code class="nohighlight nocode">mvn -Drevision=2.0.0-SNAPSHOT clean package
</code></pre>
-<p>Of course you can use the <code>.mvn/maven.config</code> file for this.</p>
+<p>Of course, you can use the <code>.mvn/maven.config</code> file for this.</p>
<p>A note about the used properties. You can only use those named
<code>${revision}</code>, <code>${sha1}</code> and/or <code>${changelist}</code> and not other
named properties like this:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -226,7 +229,8 @@ named properties like this:</p>
to have more flexibility you can use a combination of the
different properties like this:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -265,7 +269,8 @@ done via (version 1.3.1):</p>
build. We have a parent pom and one or more children.
The parent pom will look like this:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -288,7 +293,8 @@ The parent pom will look like this:</p>
</code></pre>
<p>The child will look like this:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.maven.ci</groupId>
@@ -297,7 +303,7 @@ The parent pom will look like this:</p>
</parent>
<groupId>org.apache.maven.ci</groupId>
<artifactId>ci-child</artifactId>
- ...
+ ...
</project>
</code></pre>
<p>A multi module build can of course build the same way as the single project setup. You should
@@ -308,7 +314,8 @@ between module(s). The usual way of defi
versions has been to use <code>${project.version}</code> and this has not been changed.</p>
<p>So the correct way to do such things can be seen in the following example:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -331,7 +338,8 @@ versions has been to use <code>${project
</code></pre>
<p>The child will look like this:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache.maven.ci</groupId>
@@ -340,7 +348,7 @@ versions has been to use <code>${project
</parent>
<groupId>org.apache.maven.ci</groupId>
<artifactId>ci-child</artifactId>
- ...
+ ...
<dependencies>
<dependency>
<groupId>org.apache.maven.ci</groupId>
@@ -358,7 +366,8 @@ the <a href="https://www.mojohaus.org/fl
in your repository which will not be consumable by Maven anymore. Such kind of setup
will look like this:</p>
-<pre class="prettyprint linenums"><code class="language-xml"><project>
+<pre class="prettyprint linenums"><code class="language-xml">
+<project>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
@@ -374,34 +383,34 @@ will look like this:</p>
<revision>1.0.0-SNAPSHOT</revision>
</properties>
- <build>
- <plugins>
- <plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>flatten-maven-plugin</artifactId>
- <version>1.1.0</version>
- <configuration>
- <updatePomFile>true</updatePomFile>
- <flattenMode>resolveCiFriendliesOnly</flattenMode>
- </configuration>
- <executions>
- <execution>
- <id>flatten</id>
- <phase>process-resources</phase>
- <goals>
- <goal>flatten</goal>
- </goals>
- </execution>
- <execution>
- <id>flatten.clean</id>
- <phase>clean</phase>
- <goals>
- <goal>clean</goal>
- </goals>
- </execution>
- </executions>
- </plugin>
- </plugins>
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.codehaus.mojo</groupId>
+ <artifactId>flatten-maven-plugin</artifactId>
+ <version>1.1.0</version>
+ <configuration>
+ <updatePomFile>true</updatePomFile>
+ <flattenMode>resolveCiFriendliesOnly</flattenMode>
+ </configuration>
+ <executions>
+ <execution>
+ <id>flatten</id>
+ <phase>process-resources</phase>
+ <goals>
+ <goal>flatten</goal>
+ </goals>
+ </execution>
+ <execution>
+ <id>flatten.clean</id>
+ <phase>clean</phase>
+ <goals>
+ <goal>clean</goal>
+ </goals>
+ </execution>
+ </executions>
+ </plugin>
+ </plugins>
</build>
<modules>
<module>child1</module>