This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a commit to branch update-relnotes-MNG-7887
in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit 6b24215d7e36f9f11a378c0df813ccb1cc66e132
Author: Tamas Cservenak <ta...@cservenak.net>
AuthorDate: Fri Sep 22 11:58:02 2023 +0200
[MNG-7887] Update release notes with new breakage
---
https://issues.apache.org/jira/projects/MNG/issues/MNG-7887
---
content/markdown/docs/3.9.0/release-notes.md | 1 +
content/markdown/docs/3.9.1/release-notes.md | 1 +
content/markdown/docs/3.9.2/release-notes.md | 1 +
content/markdown/docs/3.9.3/release-notes.md | 1 +
content/markdown/docs/3.9.4/release-notes.md | 1 +
5 files changed, 5 insertions(+)
diff --git a/content/markdown/docs/3.9.0/release-notes.md
b/content/markdown/docs/3.9.0/release-notes.md
index 1d71f463..841abe18 100644
--- a/content/markdown/docs/3.9.0/release-notes.md
+++ b/content/markdown/docs/3.9.0/release-notes.md
@@ -51,6 +51,7 @@ If you have any questions, please consult:
* 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).
+* 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).
### Notable Core Improvements
diff --git a/content/markdown/docs/3.9.1/release-notes.md
b/content/markdown/docs/3.9.1/release-notes.md
index 4b7c98b5..d404c3b4 100644
--- a/content/markdown/docs/3.9.1/release-notes.md
+++ b/content/markdown/docs/3.9.1/release-notes.md
@@ -49,6 +49,7 @@ The full list of changes can be found in our [issue
management system][4].
* 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).
+* 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).
## Known Issues
diff --git a/content/markdown/docs/3.9.2/release-notes.md
b/content/markdown/docs/3.9.2/release-notes.md
index 5c48b40f..b432aa66 100644
--- a/content/markdown/docs/3.9.2/release-notes.md
+++ b/content/markdown/docs/3.9.2/release-notes.md
@@ -67,6 +67,7 @@ plugin versions. For non-ASF plugins, contact plugin
maintainers to apply requir
* 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).
+* 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).
## Known Issues
diff --git a/content/markdown/docs/3.9.3/release-notes.md
b/content/markdown/docs/3.9.3/release-notes.md
index a1473e30..7d85adf0 100644
--- a/content/markdown/docs/3.9.3/release-notes.md
+++ b/content/markdown/docs/3.9.3/release-notes.md
@@ -65,6 +65,7 @@ pages for more.
* 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).
## Known Issues
diff --git a/content/markdown/docs/3.9.4/release-notes.md
b/content/markdown/docs/3.9.4/release-notes.md
index 946c6d96..8da9b2b8 100644
--- a/content/markdown/docs/3.9.4/release-notes.md
+++ b/content/markdown/docs/3.9.4/release-notes.md
@@ -52,6 +52,7 @@ The full list of changes can be found in our [issue
management system][4].
* 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).
## Complete Release Notes
