slachiewicz opened a new pull request, #106: URL: https://github.com/apache/maven-jdeps-plugin/pull/106
Fixes #105. \`jdeps\` refuses a classpath containing a multi-release JAR unless \`--multi-release\` is set, but the plugin only set it when a user explicitly configured \`<multiRelease>\`, so any dependency bump introducing one (e.g. plexus-utils since 3.5.0, hit in #102) broke the build. Verified empirically that \`--multi-release base\` is safe on an all-non-multi-release classpath and on a mixed one alike, so this now defaults to it automatically whenever any analyzed JAR is a multi-release JAR and the resolved \`jdeps\` supports the option (checked via \`jdeps -version\`, since the plugin still targets and is tested against JDK 8). A user-configured \`<multiRelease>\` is left untouched. Verified locally end-to-end against a project depending on plexus-utils 3.6.1 (the exact jar from #102): build succeeds unconfigured, with \`--multi-release base\` added automatically; a non-multi-release dependency gets no flag added. Full unit test suite, IT suite, and spotless all pass. *This change was created with AI assistance.* -- 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]
