Hi, Good idea.
One of the resolutions can be to use maven wrapper to configure the Maven version to use, and use wrapper to build a project. Such a solution can be easily used in any CI system. Using a wrapper we simply download the latest build and deployed Maven version from the repository, we don't need to build the project twice. I assume that deployment is done after all tests pass so the repository will contain a working version. Task to do before: - Make maven wrapper functional [1] - Support SNAPSHOT versions by wrapper [2] [1] https://issues.apache.org/jira/browse/MWRAPPER-14 [2] https://issues.apache.org/jira/browse/MWRAPPER-15 wt., 9 lis 2021 o 11:52 Maarten Mulders <mthmuld...@apache.org> napisał(a): > Hi all, > > In the last year, we've seen multiple situations where a change in > Maven core prevented Maven from building itself [1][2]. > > On the path to stabilising Maven towards Maven 4, I think this isn't > helping us. That's why I propose we introduce an additional GitHub > action. Let's call it the "eat our own dogfood" check: build Maven Core, > then use that build to build Maven Core again. > > Maybe it's possible to do it on Jenkins, too. I'm less familiar with our > Jenkins setup, that's all... > > What do you think? > > > Thanks, > > Maarten > > > [1] https://issues.apache.org/jira/browse/MNG-7087 > [2] https://issues.apache.org/jira/browse/MNG-7319 > -- Sławomir Jaranowski