On Fri, Feb 7, 2025 at 8:50 AM Slawomir Jaranowski <s.jaranow...@gmail.com> wrote:
> I would like to maintain both versions only for some of the core > plugins - in order to test / check the new API from Maven 4. > > As Maven 4 still supports plugins for Maven 3 - we can switch the rest > of plugins after the release final version of Maven 4. Software deployment moves a lot slower than devs would like. I don't expect Maven 4 to be more common than Maven 3 this decade. If Maven 4 isn't a drop-in replacement for Maven 3, then maybe not next decade either. When it comes to documentation, we need to prioritize what customers are using, and that's Maven 3 for the next multiple years. This will vary page by page, but the main site should be fully informative for someone using Maven 3. For non-core plugins, I'd like to see one release that works in both 3 and 4. I have multiple open PRs waiting for review and approval to remove Maven 2 cruft (and in one case Maven 1) from our own projects. There's a lot more work to be done along these lines. Until we finish Maven's own migration from the last two major versions, I don't have a lot of hope for the broader community quickly moving to Maven 4. :-( -- Elliotte Rusty Harold elh...@ibiblio.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
