rmannibucau commented on PR #765: URL: https://github.com/apache/maven/pull/765#issuecomment-1183191824
> 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. It is what is done (sadly or not) and while we don't really maintain minor branches I guess it will stay like that so must be taken into account whatever we think about it IMHO. > Those who "can upgrade maven to get new features", but "cannot update the plugins"... maybe just need better tuition about Maven? You assume again there is a new version of the plugin, keep in mind it is rarely true for anything outside maven ecosystem and in terms of metrics there are way more plugins outside org.apache.maven than inside. > Imho, it does not make sense to upgrade maven / java with the expectation that it will work forever without any migration. The plugins are definitely linked to a given maven version (range), even if maven tries to be compatible. Agree but expectation is to rarely break - and one again if a warning is printed it must not be random, current impl is equivalent to `if Math.random() > 0.5 then warning()`. > Those warnings are required in order to urge users and plugin developers to do this upgrade. That also means that we need to do the homework in our plugins too (hence the recent modifications on maven-install-plugin and maven-deploy-plugin), which should have been done a long time ago. Maybe an exit door until we get a saner ecosystem is to only do it for our own plugins and ignore (debug level?) it for external ones using the groupId? -- 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
