This is an automated email from the ASF dual-hosted git repository. cstamas pushed a commit to branch maven-3913 in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit ee8050498197babed1ee159088e5d4b77ffec125 Author: Tamas Cservenak <[email protected]> AuthorDate: Mon Mar 2 15:14:08 2026 +0100 Maven 3.9.13 release notes --- content/markdown/docs/3.9.13/release-notes.md | 80 +++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) diff --git a/content/markdown/docs/3.9.13/release-notes.md b/content/markdown/docs/3.9.13/release-notes.md new file mode 100644 index 00000000..5d28430f --- /dev/null +++ b/content/markdown/docs/3.9.13/release-notes.md @@ -0,0 +1,80 @@ +<!-- +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.9.13 Release Notes + +The Apache Maven team would like to announce the release of Maven 3.9.13. + +Maven 3.9.13 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.9.13/](/ref/3.9.13/) + +## Overview About the Changes + +Regression fixes and other improvements from Maven 3.9.12. All users already on Maven 3.9.x are advised to upgrade. + +The majority of fixed issues are bug and regression fixes for user reported problems. + +### Notable Changes in Maven 3.9.13 + +- Maven plugin prerequisites check now properly supports ranges when Java 8 (or 1.8) is specified. +- Plexus Security Dispatcher was still enlisted as Plexus component in Maven `components.xml`, while it was migrated to JSR330. This caused warnings on Java 26+ as Plexus did field injection into `final` fields of it. +- Plugin versions in default bindings are updated. + +This release updates Resolver to version [1.9.27](https://github.com/apache/maven-resolver/releases/tag/maven-resolver-1.9.27). + +### Notable Changes in Resolver 1.9.27 + +- Parallel PUT change happened in Resolver 1.9.25 was undone, as many MRM struggle with concurrent HTTP requests. +- Treat HTTP 410 status code as 404 in artifact resolution. Resolver will by default now cache 410 response in say way as 404 is. +- Apache HTTP transport got fixes regarding proxies. +- Locally cached artifacts were "escaping" RRF + +## Full changelog + +For a full list of changes, please refer to the [GitHub release page](https://github.com/apache/maven/releases/tag/maven-3.9.13). + +## Known issues + +No known issues. + +## Potentially Breaking Core Changes (if migrating from 3.8.x) + +* The Maven Resolver transport has changed from Wagon to "native HTTP", see [Resolver Transport guide](/guides/mini/guide-resolver-transport.html). +* Maven 2.x was auto-injecting an ancient version of `plexus-utils` dependency into the plugin classpath, and Maven 3.x continued doing this to preserve backward compatibility. Starting with Maven 3.9, it does not happen anymore. This change may lead to plugin breakage. The fix for affected plugin maintainers is to explicitly declare a dependency on `plexus-utils`. The workaround for affected plugin users is to add this dependency to plugin dependencies until issue is fixed by the affect [...] +* Mojos are prevented to bootstrap new instance of `RepositorySystem` (for example by using deprecated `ServiceLocator`), they should reuse `RepositorySystem` instance provided by Maven instead. See [MNG-7471](https://issues.apache.org/jira/browse/MNG-7471). +* Each line in `.mvn/maven.config` is now interpreted as a single argument. That is, if the file contains multiple arguments, these must now be placed on separate lines, see [MNG-7684](https://issues.apache.org/jira/browse/MNG-7684). +* System and user properties handling cleanup, see [MNG-7556](https://issues.apache.org/jira/browse/MNG-7556). As a consequence, this may introduce breakage in environments where the user properties were used to set system properties or other way around, for example see [MNG-7887](https://issues.apache.org/jira/projects/MNG/issues/MNG-7887). +* 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. + +## 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 +
