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

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to