[
https://issues.apache.org/jira/browse/MNG-8649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947105#comment-17947105
]
Tim te Beek commented on MNG-8649:
----------------------------------
Great to hear you're looking to help automate migrations to Maven 4. If there's
any interest in using OpenRewrite to do so I'd love to collaborate with you
all. On our end we've already automated some of the necessary steps, as part of
[our Maven best practices
recipe,|https://docs.openrewrite.org/recipes/maven/bestpractices] and we're
looking to do more as needed.
I'll let you weigh your options, but you know how to reach me if needed. :)
> Maven 4 migration tool
> ----------------------
>
> Key: MNG-8649
> URL: https://issues.apache.org/jira/browse/MNG-8649
> Project: Maven
> Issue Type: Task
> Reporter: Guillaume Nodet
> Priority: Critical
>
> We should be able to help our users to migrate to Maven 4.
> This can be done in several steps:
> * fix POMs (not necessarily migrate to 4.1.0 model, but fix any deprecated
> construct)
> * update to more recent versions of plugins (some are known to have problems
> with Maven 4)
> * if the project is a plugin, we can try applying the draft
> https://gist.github.com/gnodet/c297ccae07dd2ee67dfa98cf1ef128f9
> This may be implemented as a plugin or as a tool in the mvnsh script somehow.
> A lot of failures for the first point can be found at
> https://github.com/gnodet/maven4-testing/issues/2812.
> It would be nice to alter the workflow above so that, in case of failure, the
> migration tool is run and another attempt is done.
> Ideally, the workflow would raise an issue on the project to track progress
> in case the initial build fails (it may be difficult to track the link so
> that we don't create a new issue each time we run the workflow).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
