slachiewicz opened a new issue, #1796:
URL: https://github.com/apache/maven-mvnd/issues/1796
### Observed during
A full reactor build of maven-mvnd 1.0.7-SNAPSHOT (with Maven 4.0.0-rc-7,
JDK 21).
mvnd currently has skipped tests without a path to re-enabling them:
1. `mvnd-common` — `SocketFamilyTest#testUnixFromTo` (1 skipped):
`@Disabled("Test framework does not support multi-release expanded jars")`
The test framework presumably loads mvnd-common from a plain directory;
making the harness handle MR-JARs would let this run again.
2. `mvnd-client` — `EnvHelperTest` (1 skipped): bare `@Disabled` with **no
reason**.
Given mvnd-1.x still targets Java 8 bytecode, it would be good to (a)
document every `@Disabled` with a reason, (b) track what it would take to
re-enable each test.
Note: other skipped tests seen in the wider reactor build live in other
repos (e.g. `maven-build-cache-extension` `XmlServiceTest` — all 4 tests
disabled, tracked separately; and several bare `@Disabled` in maven core tests
such as `ConditionProfileActivatorTest`, `MavenCliTest`, `MavenInvokerTest`,
`FileModelSourceTest`, `DefaultWagonManagerTest`).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
