This is an automated email from the ASF dual-hosted git repository. cstamas pushed a commit to branch maven-3913-known-issue in repository https://gitbox.apache.org/repos/asf/maven-site.git
commit 2431d9b180c6f740cca74b3543c1d55750b895c9 Author: Tamas Cservenak <[email protected]> AuthorDate: Mon Mar 9 11:33:10 2026 +0100 Maven 3.9.13 known issue --- content/markdown/docs/3.9.13/release-notes.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/content/markdown/docs/3.9.13/release-notes.md b/content/markdown/docs/3.9.13/release-notes.md index 062e249e..c993049a 100644 --- a/content/markdown/docs/3.9.13/release-notes.md +++ b/content/markdown/docs/3.9.13/release-notes.md @@ -58,7 +58,12 @@ For a full list of changes, please refer to the [GitHub release page](https://gi ## Known issues -No known issues. +After the release, we discovered that the distribution contains several testing libraries, see [GH-11762](https://github.com/apache/maven/issues/11762). +While this is not an issue per se (maven-core does not export these dependencies, they are "confined" in core classloader), in case you perform +dependency analysis (ie using Enforcer) **and** you depend on `maven-core` or any artifact that has `maven-core` in its tree, you may hit issues. +In this case, remaining on 3.9.12 release is the recommended workaround. + +We are working on 3.9.14 release with this issue fixed, and it will happen as soon as possible. ## Potentially Breaking Core Changes (if migrating from 3.8.x)
