Page History

...

• Documentation "how to upgrade plugins to Maven 4 API"? SITE-issue 751
• Not a direct blocker for GA release, but I (Gerd, additions on list by Matthias) think Maven (Plugins) should (always) compile/test with the latest 4.x (at least if they are already ported to 4.x). I made some tries on my local machine (macOS). Some components need 4.x, but seem to only work with specific versions:
  Unfortunately, there were API changes between the beta/rcs which require updates of the code.
  Therefore, we should also check if the latest published version of each 4.x component, runs with latest 4.x (independent from the version it needs to build).
• conclusion discussion end of March 2026: https://lists.apache.org/list.html?dev@maven.apache.org, with small summary by Guillaume
  

  Info

  On the @Experimental api, I just want to restate what I had in mind : * release 4.0 without publicizing the new API * finalize 4.x plugins to make them ready for consumption, this could use a few iterations of Maven over the coming months (4.1, 4.2, etc...) * when that's done, remove the @Experimental flag and release all plugins in GA Basically, ship the API in a "tech preview" mode. We don't make the API public, we don't tell people to migrate their plugins yet... But 4.0 brings much more than the API...

• tracking of Maven's Maven 3 plugin plugins build with Maven 4 is the real target for Maven 4.0 (and if possible non-Maven ones, like Mojohaus)
  To check on our own plugins that the Maven 3 compatibility in Maven 4 works at scale, and eventually fix a few edge cases

...