rmannibucau commented on issue #11255: URL: https://github.com/apache/maven/issues/11255#issuecomment-3400334799
> Anymore, people will not look at the poms, they just trust the update process from tooling like dependabot or renovatebot. open bugs in these tools maybe, maven looks covered with a clear path from your description but agree the ecosystem doesn't always handle it cause relocations are not just switches they are sometimes literally used for replacement with totally different content my 2cts is that there you can look at any automotion but the best would be a mp-maven-plugin which does the migration (spring roo/jboss forge/quarkus like) > it'll take a whole lot for everybody to migrate was not really the care for jakarta, people did migrate quickly enough (<1 year) or not so I wouldn't care about that > Maybe, but we don't want to repeat this for MP do we? so do not relocate, there is no real reason to do, eclipse can get microprofile naming and be 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
