Bukama commented on issue #751: URL: https://github.com/apache/maven-site/issues/751#issuecomment-2781325354
> question: is it from a plugin user perspective? or from a plugin maintainer perspective? This topic here aims for plugin maintainers, not for users. #729 aims for users. For that (see my working file at https://github.com/Bukama/maven-site/blob/i729_maven4migguide/content/markdown/guides/mini/guide-migration-to-mvn4.md ) I currently wrote > Note: While Maven 4.0.0 aims to support all Maven 3.9 compatible plugins, this can not be guaranteed for custom plugins which use outdated plugin API methods. I chose this wording, because I wanted to make clear that a well maintained plugin (not only the official ones) will work, but we can not promise it for custom ones. > then in the future, plugin maintainer will have choice to create a Maven 4 specific release of their plugin, that won't work in Maven 3 > the tricky question being: maintain 2 branches in parallel? for how much time? I agree that we should mention it in the guide and also that it will take time until most users have switched, but we should also add that each developer needs to decide that for his owns. It's their time and effort they put into it. -- 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
