This is an automated email from the ASF dual-hosted git repository.
cstamas 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 4191cd9a Extend release notes for 3.9.0 (#381)
4191cd9a is described below
commit 4191cd9afd142f7fac756c827f2306d8c3a92bd2
Author: Tamas Cservenak <[email protected]>
AuthorDate: Tue Feb 7 10:53:07 2023 +0100
Extend release notes for 3.9.0 (#381)
Extend release note and enumerate breaking changes, improvements...
---------
Co-authored-by: Guillaume Nodet <[email protected]>
---
content/markdown/docs/3.9.0/release-notes.md | 29 +++++++++++++++++++++++++++-
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/content/markdown/docs/3.9.0/release-notes.md
b/content/markdown/docs/3.9.0/release-notes.md
index 14c12aee..94ac9bf0 100644
--- a/content/markdown/docs/3.9.0/release-notes.md
+++ b/content/markdown/docs/3.9.0/release-notes.md
@@ -41,9 +41,36 @@ If you have any questions, please consult:
* Minimum Java version to use with Maven 3.9.0 is raised to Java 8.
* With Java 8, upgrade of several key dependencies became possible as well.
* Several backports from Maven 4.x line.
-* Long outstanding issue fixes from Maven 3.8.x line.
+* Long outstanding issue fixes from Maven 3.x line.
+* Cutting ties with Maven 2 backward compatibility, preparing grounds for
Maven 4.
* General fixes and improvements.
+### Potentially Breaking Core Changes
+
+* 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 boostrap 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).
+
+### Notable Core Improvements
+
+* Help with projects maintenance: Maven now warns about use of deprecated
plugins, goals, parameters, etc.
+* Add support for "mvn pluginPrefix:version:goal" invocation, and align
console logging as well (make it copy-paste-able).
+* Add profile activation by packaging.
+* Maven 3.9.0 is now fully compatible with new 3.x line of install and deploy
plugins (previous versions warns about this).
+
+### Notable Resolver 1.9.x Improvements
+
+* Shared local repository (advisory file locking, Hazelcast or Redis, see
[documentation](https://maven.apache.org/resolver/local-repository.html#shared-access-to-local-repository)).
+* Split local repository, plus "workspace" support for branched development
(see
[documentation](https://maven.apache.org/resolver/local-repository.html#split-local-repository)).
+* Switchable and alternative resolver transports included, with default
switched to native transport.
+* Pluggable checksum algorithms API (is not tied to MessageDigest anymore, see
[documentation](https://maven.apache.org/resolver/about-checksums.html)).
+* Choice of resolver collectors: a new BF collector (with parallel POM
downloads) has been added along the existing DF one.
+* Remote repository filtering (see
[documentation](https://maven.apache.org/resolver/remote-repository-filtering.html)).
+* Trusted checksum sources (ability to provide some or all artifact checksums
ahead of time).
+* Pluggable artifact resolver post-processor, with "trustedChecksums"
implementation.
+* Chained local repository (for IT isolation between "outer" and "inner"
builds).
+* Recording reverse dependency tree tracking information into local repository.
+
The full list of changes can be found in our [issue management system][4].
## Known Issues
