gnodet commented on PR #12135: URL: https://github.com/apache/maven/pull/12135#issuecomment-6012371566
> what about ignoring compat module and keep them intended for classpath? will avoid the split package/api breakage hell and since it is compat they are intended to go away at some point in the future so no need to invest in them IMHO Thanks for the suggestion — that's actually exactly what the PR does. All 13 compat modules only get an Automatic-Module-Name manifest entry (no module-info.java), so they remain on the classpath and the split-package issue is avoided entirely. The PR description has a "Modules with Automatic-Module-Name only" section that covers this. Is there something specific in the current approach that you think still needs to be changed, or were you perhaps not seeing the compat modules handled that way? -- 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]
