slachiewicz commented on PR #1702:
URL: https://github.com/apache/maven-mvnd/pull/1702#issuecomment-5172382378
This bump is what turns the native builds red. Root cause, for the record:
1.1.6 introduced `NativeCompileNoForkMojo.generateBaseSBOMIfNeeded`, and its
call chain reaches `isColorEnabled()`, implemented in 1.1.6 as `return
MessageUtils.isColorEnabled();` (`AbstractNativeImageMojo.java:313`).
`maven-shared-utils` is neither a declared dependency of the plugin nor
exported by the Maven core realm, so every native build dies with:
```
Caused by: java.lang.NoClassDefFoundError:
org/apache/maven/shared/utils/logging/MessageUtils
at AbstractNativeImageMojo.isColorEnabled
(AbstractNativeImageMojo.java:314)
at AbstractNativeImageMojo.addConsoleColorArgument
(AbstractNativeImageMojo.java:305)
at AbstractNativeImageMojo.getBuildArgs
(AbstractNativeImageMojo.java:250)
at NativeCompileNoForkMojo.generateBaseSBOMIfNeeded
(NativeCompileNoForkMojo.java:166)
```
It is not macOS-specific and not Maven-version-specific — nothing puts
`maven-shared-utils` on that plugin realm on any platform.
1.1.7 fixes it upstream by dropping the reference in favour of the plugin's
own `getMavenColorSetting()` / `parseMavenColorMode()` reading `style.color`.
Checked against the jars: 1.1.6's `AbstractNativeImageMojo.class` carries the
`MessageUtils` constant-pool reference, 1.1.3's does not, and 1.1.7 has zero
occurrences.
So the right move is 1.1.7, not a pin at 1.1.3. Replacement PRs: #1708 for
`mvnd-1.x`, #1706 for `master`.
--
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]
