This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a commit to branch maven-398-release-notes
in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit ffbba602431fef0ffaf09547d0217c7650b62558
Author: Tamas Cservenak <ta...@cservenak.net>
AuthorDate: Thu Jun 13 09:44:23 2024 +0200
Maven 3.9.8 release notes
---
content/markdown/docs/3.9.8/release-notes.md | 79 ++++++++++++++++++++++++++++
1 file changed, 79 insertions(+)
diff --git a/content/markdown/docs/3.9.8/release-notes.md
b/content/markdown/docs/3.9.8/release-notes.md
new file mode 100644
index 00000000..7a591d09
--- /dev/null
+++ b/content/markdown/docs/3.9.8/release-notes.md
@@ -0,0 +1,79 @@
+<!--
+ 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.
+
+ NOTE: For help with the syntax of this file, see:
+ http://maven.apache.org/doxia/modules/index.html#Markdown
+-->
+
+# Release Notes – Maven 3.9.8
+
+The Apache Maven team would like to announce the release of Maven 3.9.8.
+
+Maven 3.9.8 is [available for download][0].
+
+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.
+
+The core release is independent of plugin releases. Further releases of
plugins will be made separately. See the [PluginList][1] for more information.
+
+If you have any questions, please consult:
+
+- the web site: [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.8/](/ref/3.9.8/)
+
+## Overview About the Changes
+
+Regression fixes and other improvements from Maven 3.9.7. All users already on
Maven 3.9.x are advised to upgrade.
+
+Bug fixes ranges from restored ability (lost in 3.9.7) to build some project
that depends on artifact with invalid POMs,
+OS profile activation issues and many other minor but annoying bugs.
+
+Improvements on other hand include added logging of those invalid POMs (in
DEBUG even telling what is the problem with them),
+improved output for plugin validation and alike.
+
+The "known issue" from 3.9.7, the
[MNG-8116](https://issues.apache.org/jira/browse/MNG-8116) bug was fixed as
well, by updating to
+latest Eclipse Sisu release 0.9.0.M3 that carries ASM 9.7 (Java 23).
+
+Finally, Maven 3.9.8 went thru a "diet", and lost commons-lang from it's
constituents. This change has no effect on plugins (as
+commons-lang was never published artifact by Core), while extensions, that do
depend on presence of it hopefully did declare it as
+dependency (as would be best practice).
+
+The full list of changes can be found in our [issue management system][4].
+
+### Known issues ###
+
+None.
+
+### 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][5]
+
+[0]: ../../download.html
+[1]: ../../plugins/index.html
+[2]: https://maven.apache.org/
+[4]:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354748
+[5]: ../../docs/history.html
