cstamas commented on PR #765: URL: https://github.com/apache/maven/pull/765#issuecomment-1183057949
> @cstamas exactly my point, you can upgrade maven to get new features (better jvm.config support, better CLI, optims, ...) but not the plugins and it must works without warnings until the API got broken AND the plugin uses this breaking change. No, my point is quite the opposite :smile: IF you want to keep yourself up to date your Maven build, you need to consider your build as whole (maven + plugins, not just "bits" from it), not just the CLI, and, once you step over major version like 3.x to 4.x, you should not expect your 2.x plugins to work. And we should make this obvious to users as soon as possible. Those who "can upgrade maven to get new features", but "cannot update the plugins"... maybe just need better tuition about Maven? Better docs? I mean, to me yet another contradiction: "update work tools" but "not plugins", while our doco is clear that plugins are "build tools" as well (from doco "Build plugins will be executed during the build ").... -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
