slachiewicz commented on issue #13302: URL: https://github.com/apache/maven/issues/13302#issuecomment-5919808571
> Maven 4.0.0 is not out: cannot we wait a little bit before creating double maintenance? I know it is funny to use AI and burn tokens, but it's not funny to augment the maintenance @hboutemy its to validate where we are with Maven 4 API, if we have some blockers, missing features. Looking at results - I don't have apetite to release any new Maven 4 only component/plugin but few design things we need to take. Next step after collecting results, in pararel to design decisions is to simplify/move away from deprecated or soon to be deprecated iun V3 api to simplify future Maven 4 migration. For Doxia i've identifued also few points that needs more effort. I also remember about Your's proposal to move V4 from master to the dedicated branches to focus on V3 improvements instead (to run on Maven 3.10 and Maven 4) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
