This is an automated email from the ASF dual-hosted git repository.

slawekjaranowski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 6658b4a7 Maven 3.10.1 release notes (#1827)
6658b4a7 is described below

commit 6658b4a738e4ec234f87565e9fe5c876cc175d93
Author: Tamas Cservenak <[email protected]>
AuthorDate: Sun Nov 15 15:04:52 2026 +0100

    Maven 3.10.1 release notes (#1827)
    
    * Maven 3.10.1 release notes
    
    * Apply suggestion from @cstamas
    
    * add known issue - hard links
    
    * Add note about colored output
    
    Co-authored-by: Slawomir Jaranowski <[email protected]>
    
    * Apply suggestion from @Bukama
    
    * Point the site at 3.10.1 and fix wording in its release notes
    
    The history row drops the 3.10.0 announcement link; the release date and
    the 3.10.1 announcement link go in once the release is announced.
    
    ---------
    
    Co-authored-by: Slawomir Jaranowski <[email protected]>
    Co-authored-by: Matthias Bünger <[email protected]>
    Co-authored-by: Sylwester Lachiewicz <[email protected]>
---
 content/markdown/docs/3.10.1/release-notes.md | 135 ++++++++++++++++++++++++++
 content/markdown/docs/history.md.vm           |   3 +-
 pom.xml                                       |   8 +-
 3 files changed, 141 insertions(+), 5 deletions(-)

diff --git a/content/markdown/docs/3.10.1/release-notes.md 
b/content/markdown/docs/3.10.1/release-notes.md
new file mode 100644
index 00000000..cd3499f1
--- /dev/null
+++ b/content/markdown/docs/3.10.1/release-notes.md
@@ -0,0 +1,135 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Maven 3.10.1 Release Notes
+
+The Apache Maven team would like to announce the release of Maven 3.10.1.
+
+Maven 3.10.1 is [available for download][0].
+
+The core release is independent of plugin releases. Further releases of 
plugins will be made separately. See the [Plugin list][1] for more information.
+
+If you have any questions, please consult:
+
+- the website: [https://maven.apache.org/][2]
+- the maven-user mailing list: 
[https://maven.apache.org/mailing-lists.html](/mailing-lists.html)
+- the reference documentation: 
[https://maven.apache.org/ref/3.10.1/](/ref/3.10.1/)
+
+## Overview About the Changes
+
+The main driver for new generation was to align Maven 3 and 4 majors versions 
on same Resolver version. Hence, Maven 3.10 is now using Resolver 2.0 lineage, 
same one that is used by Maven 4+. On the other hand, at "Maven level", changes 
are kept minimal, and upgrading should be pretty straightforward. Also, 3.10 
received many security and other enhancements as well. Still, most of the 
changes happened "under the surface", end users might even be unaware of them. 
The key changes are liste [...]
+
+Maven 3.10.1 requires Java 8 or above to run, same as the Maven 3.9.x lineage.
+
+## Notable Changes in Maven 3.10.1
+
+Maven 3.10.1 is a bugfix release for 3.10.0. It fixes regressions reported 
after 3.10.0, backports fixes from Maven 4, and makes startup lighter.
+
+### New Features and Improvements
+
+Release 3.10.1 focused on fixing all the regressions, but there are still some 
features being added:
+
+- **Optional profiles with `-P ?id`.** Same syntax as Maven 4, so a single 
command line works for both.
+- **Maven 4 `MessageBuilderFactory` for plugins.** Plugins built against 
`maven-api-core` 4.x can inject 
`org.apache.maven.api.services.MessageBuilderFactory` on 3.10 and get colored 
output, the same as on Maven 4.
+- **JLine is gone, colors remain.** Maven no longer ships the JLine terminal 
stack (native libraries, a background setup thread, System.out/err 
replacement). Colored output is now plain ANSI escape codes, and 
`maven.style.*` overrides still apply. Startup overhead added in 3.10.0 is 
gone. JAnsi compatibility is kept through a shim.
+
+### Regression fixes
+
+There are too many to list here; see the full changelog below.
+
+## Full changelog
+
+For a full list of changes, please refer to the [GitHub release 
page](https://github.com/apache/maven/releases/tag/maven-3.10.1).
+
+## Known issues
+
+### Warning with stack trace during `install` when hard links are not supported
+
+If the build directory and the local repository are on different volumes, hard 
links
+cannot be created and Maven Resolver falls back to copying. Artifacts are 
installed correctly,
+but a `WARNING` with a full stack trace (`Invalid cross-device link`) is 
logged.
+
+To turn off hard linking and the warning, use 
`-Daether.installer.hardLink=false`
+(on the command line or in `.mvn/maven.config`).
+
+### No colored output by default in Windows `cmd.exe`
+
+To enable colors, use `--color=always` on the command line, in 
`.mvn/maven.config`,
+or in the `MAVEN_ARGS` environment variable.
+Other terminals available by default are not affected.
+
+## Potentially Breaking Core Changes (if migrating from 3.9.x)
+
+### Stricter POM validation
+
+Maven 3.10.0 raises the POM validation level: many WARNINGs from the 3.9 
lineage (in fact, from the 3.1 lineage) will
+now FAIL the build. Things like duplicated dependency entries or duplicated 
plugin entries will not be tolerated
+anymore. This aspect was not changed since Maven 3.1 lineage, and was really 
time to force users to clean up their
+POMs. The checks promoted to errors for the project being built are the 3.1 
level ones: duplicated plugins, invalid
+characters in a version, malformed snapshot versions and reserved or malformed 
repository ids. Dependencies keep being
+validated at the minimal level (and failure lead to transitive dependencies 
not being available). 
+`relativePath` of a parent is validated as well, which no Maven 3.x version 
did so far.
+To temporarily disable the stricter validation add 
`-Dmaven.resolver.validation=off` to your Maven invocation.
+
+### Classpath ordering change
+
+Dependency classpath ordering changed from "pre-order" (depth-first) to 
"level-order" (breadth-first),
+aligning with Maven 4 behavior and Resolver 2.x defaults.
+
+To restore the previous behavior, add 
`-Daether.system.dependencyVisitor=preOrder` to your Maven invocation.
+
+### Changes in the Super POM
+
+- removed deprecated `release-profile`; each project should have its own 
release profile
+- removed plugin management; each project should have its own plugin management
+- set default values for `project.build.sourceEncoding` and 
`project.reporting.outputEncoding` to `UTF-8`
+- set a default value for `project.build.outputTimestamp`, which makes builds 
reproducible by default
+
+### Artifact and metadata validation in Resolver
+
+Resolver 2.x validates artifact and metadata coordinates, and rejects values 
that cannot be safely mapped to a
+repository layout. A build relying on non-conformant coordinates can be 
unblocked with `maven.resolver.validation`
+set to `mild` or `off`, but the coordinates should be fixed instead.
+
+### Repository credentials are scoped
+
+Credentials of a `settings.xml` server are only offered to repositories and 
mirrors whose origin Maven could associate
+with that server id. Origins Maven cannot securely associate via id can be 
declared with `<repositoryOrigins>`, see
+[Server Repository Origins](/settings.html#Server_Repository_Origins).
+
+### Plugin validation
+
+Plugins and extensions used by your build are checked against Maven supported 
APIs and conventions: this "plugin
+validation" may report WARNINGs at the end of your build. See [plugin 
validation documentation](../../guides/plugins/validation/)
+to better understand what to do when your build suffers from such warnings.
+
+### Reproducible Builds
+
+Reproducible Builds is active by default, and with a fixed timestamp value for 
archive entries:
+if you rely on timestamp value for your consumption, updating timestamp value 
during release or even
+disabling Reproducible Builds may be a choice: see 
[FAQ](/guides/mini/guide-reproducible-builds.html).
+
+## Complete Release Notes
+
+See [complete release notes for all versions][3]
+
+[0]: ../../download.html
+[1]: ../../plugins/index.html
+[2]: https://maven.apache.org/
+[3]: ../../docs/history.html
diff --git a/content/markdown/docs/history.md.vm 
b/content/markdown/docs/history.md.vm
index 01839fdd..f38717e0 100644
--- a/content/markdown/docs/history.md.vm
+++ b/content/markdown/docs/history.md.vm
@@ -113,7 +113,8 @@ $esc.h$esc.h Maven 3.10.x+
 <!--  release( date version announce latest-minor jdk rowspan ) -->
 <!-- The following two lines needs to be fixed in x days if the archive picks 
up the announcement mail. -->
 
-#release( "2026-09-27" "3.10.0" 
"https://lists.apache.org/thread.html/zn01tzgl9l7sbxzs38lknhdpcovcov4h"; "true" 
"Java 8" "2" )
+#release( "2026-09-27" "3.10.1" "" "true" "Java 8" "3" )
+#release( "2026-09-27" "3.10.0" 
"https://lists.apache.org/thread.html/zn01tzgl9l7sbxzs38lknhdpcovcov4h"; "" "" 
"" )
 #release( "2026-07-09" "3.10.0-rc-1" 
"https://lists.apache.org/thread/8mqy3w0yz0d1rr0t0ctsct874qb2orq9"; "" "" "" )
 
 </table>
diff --git a/pom.xml b/pom.xml
index 0e9d0e1f..de7df40a 100644
--- a/pom.xml
+++ b/pom.xml
@@ -56,15 +56,15 @@
     <maven.site.path>maven-site</maven.site.path>
     <project.build.outputTimestamp>x</project.build.outputTimestamp>
     <!-- disable Reproducible Builds that makes the site build time fixed at 
last release time -->
-    <currentStableVersion>3.10.0</currentStableVersion>
-    
<currentStableVersionDetails>c43a36b8d67be7e0805a411bc0898af1a51f5472</currentStableVersionDetails>
-    <current310xVersion>3.10.0</current310xVersion>
+    <currentStableVersion>3.10.1</currentStableVersion>
+    
<currentStableVersionDetails>3afd8084b5629f80b97750906a719879ed4cd283</currentStableVersionDetails>
+    <current310xVersion>3.10.1</current310xVersion>
     <current4xVersion>4.0.0-rc-7</current4xVersion>
     <current39xVersion>3.9.16</current39xVersion>
     <currentMvnd1xVersion>1.0.6</currentMvnd1xVersion>
     <currentMvnd2xVersion>2.0.0-rc-3</currentMvnd2xVersion>
     
<versions2x>2.2.1,2.2.0,2.1.0,2.0.11,2.0.10,2.0.9,2.0.8,2.0.7,2.0.6,2.0.5,2.0.4,2.0.3,2.0.2,2.0.1,2.0</versions2x>
-    
<versions3x>3.10.0,3.9.16,3.9.15,3.9.14,3.9.13,3.9.12,3.9.11,3.9.10,3.9.9,3.9.8,3.9.7,3.9.6,3.9.5,3.9.4,3.9.3,3.9.2,3.9.1,3.9.0,3.8.9,3.8.8,3.8.7,3.8.6,3.8.5,3.8.4,3.8.3,3.8.2,3.8.1,3.6.3,3.6.2,3.6.1,3.6.0,3.5.4,3.5.3,3.5.2,3.5.0,3.5.0-beta-1,3.5.0-alpha-1,3.3.9,3.3.3,3.3.1,3.2.5,3.2.3,3.2.2,3.2.1,3.1.1,3.1.0,3.1.0-alpha-1,3.0.5,3.0.4,3.0.3,3.0.2,3.0.1,3.0,3.0-beta-3,3.0-beta-2,3.0-beta-1,3.0-alpha-7,3.0-alpha-6,3.0-alpha-5,3.0-alpha-4,3.0-alpha-3</versions3x>
+    
<versions3x>3.10.1,3.10.0,3.9.16,3.9.15,3.9.14,3.9.13,3.9.12,3.9.11,3.9.10,3.9.9,3.9.8,3.9.7,3.9.6,3.9.5,3.9.4,3.9.3,3.9.2,3.9.1,3.9.0,3.8.9,3.8.8,3.8.7,3.8.6,3.8.5,3.8.4,3.8.3,3.8.2,3.8.1,3.6.3,3.6.2,3.6.1,3.6.0,3.5.4,3.5.3,3.5.2,3.5.0,3.5.0-beta-1,3.5.0-alpha-1,3.3.9,3.3.3,3.3.1,3.2.5,3.2.3,3.2.2,3.2.1,3.1.1,3.1.0,3.1.0-alpha-1,3.0.5,3.0.4,3.0.3,3.0.2,3.0.1,3.0,3.0-beta-3,3.0-beta-2,3.0-beta-1,3.0-alpha-7,3.0-alpha-6,3.0-alpha-5,3.0-alpha-4,3.0-alpha-3</versions3x>
     
<version4x>4.0.0-rc-7,4.0.0-rc-6,4.0.0-rc-5,4.0.0-rc-4,4.0.0-rc-3,4.0.0-rc-2,4.0.0-rc-1,4.0.0-beta-5,4.0.0-beta-4,4.0.0-beta-3,4.0.0-alpha-13,4.0.0-alpha-12,4.0.0-alpha-10,4.0.0-alpha-9,4.0.0-alpha-8,4.0.0-alpha-7,4.0.0-alpha-5,4.0.0-alpha-4,4.0.0-alpha-3,4.0.0-alpha-2</version4x>
     <site.output>${project.build.directory}/site</site.output>
     <javaVersion>17</javaVersion>

Reply via email to