Maybe we should add the enforcer rule to enforce scope? :D
Am 08.03.2026 um 00:33 schrieb Tamás Cservenák:
Agreed, this must be fixed asap.
T
On Sun, Mar 8, 2026, 00:03 Michael Osipov <[email protected]> wrote:
On 2026/03/07 22:56:50 Michael Osipov wrote:
Tamás,
something isn't right:
Only in apache-maven-3.9.13/lib: apiguardian-api-1.1.2.jar
Only in apache-maven-3.9.13/lib: asm-9.9.1.jar
Only in apache-maven-3.9.12/lib: asm-9.9.jar
Only in apache-maven-3.9.12/lib: commons-codec-1.20.0.jar
Only in apache-maven-3.9.13/lib: commons-codec-1.21.0.jar
Only in apache-maven-3.9.13/lib: junit-jupiter-api-5.14.2.jar
Only in apache-maven-3.9.13/lib: junit-platform-commons-1.14.2.jar
Only in apache-maven-3.9.12/lib: maven-artifact-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-artifact-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-builder-support-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-builder-support-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-compat-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-compat-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-core-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-core-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-embedder-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-embedder-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-model-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-model-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-model-builder-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-model-builder-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-plugin-api-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-plugin-api-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-repository-metadata-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-repository-metadata-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-resolver-api-1.9.25.jar
Only in apache-maven-3.9.13/lib: maven-resolver-api-1.9.27.jar
Only in apache-maven-3.9.12/lib:
maven-resolver-connector-basic-1.9.25.jar
Only in apache-maven-3.9.13/lib:
maven-resolver-connector-basic-1.9.27.jar
Only in apache-maven-3.9.12/lib: maven-resolver-impl-1.9.25.jar
Only in apache-maven-3.9.13/lib: maven-resolver-impl-1.9.27.jar
Only in apache-maven-3.9.12/lib: maven-resolver-named-locks-1.9.25.jar
Only in apache-maven-3.9.13/lib: maven-resolver-named-locks-1.9.27.jar
Only in apache-maven-3.9.12/lib: maven-resolver-provider-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-resolver-provider-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-resolver-spi-1.9.25.jar
Only in apache-maven-3.9.13/lib: maven-resolver-spi-1.9.27.jar
Only in apache-maven-3.9.12/lib:
maven-resolver-transport-file-1.9.25.jar
Only in apache-maven-3.9.13/lib:
maven-resolver-transport-file-1.9.27.jar
Only in apache-maven-3.9.12/lib:
maven-resolver-transport-http-1.9.25.jar
Only in apache-maven-3.9.13/lib:
maven-resolver-transport-http-1.9.27.jar
Only in apache-maven-3.9.12/lib:
maven-resolver-transport-wagon-1.9.25.jar
Only in apache-maven-3.9.13/lib:
maven-resolver-transport-wagon-1.9.27.jar
Only in apache-maven-3.9.12/lib: maven-resolver-util-1.9.25.jar
Only in apache-maven-3.9.13/lib: maven-resolver-util-1.9.27.jar
Only in apache-maven-3.9.12/lib: maven-settings-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-settings-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-settings-builder-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-settings-builder-3.9.13.jar
Only in apache-maven-3.9.12/lib: maven-slf4j-provider-3.9.12.jar
Only in apache-maven-3.9.13/lib: maven-slf4j-provider-3.9.13.jar
Only in apache-maven-3.9.13/lib: opentest4j-1.3.0.jar
Only in apache-maven-3.9.12/lib: org.eclipse.sisu.inject-0.9.0.M4.jar
Only in apache-maven-3.9.13/lib: org.eclipse.sisu.inject-1.0.0.jar
Only in apache-maven-3.9.12/lib: org.eclipse.sisu.plexus-0.9.0.M4.jar
Only in apache-maven-3.9.13/lib: org.eclipse.sisu.plexus-1.0.0.jar
Only in apache-maven-3.9.13/lib: plexus-testing-2.1.0.jar
Only in apache-maven-3.9.13/lib: plexus-testing.license
Why do we have test dependencies in the deliverable?
Oversight in:
commit 87408ac656fedb44585b24ac1dec1520fb23aa5e
Author: Slawomir Jaranowski <[email protected]>
Date: 2025-12-21T11:08:52+01:00
Migrate to JUnit 5 - avoid using TestCase (#11547)
* Migrate to JUnit 5 - avoid using TestCase
Only simply migration to remove usage of JUnit 3 - TestCase
More improvements to tests can be done in the future.
plexus-testing has been introduced and scope is missing. Moreover the
version should have been a property...
I think we need a fix and a new release.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
