Hello Paul, Did you check maven extensions? You can rewrite the pom programmatically - and respect maven rules whatever initial state is in the pom - without patching maven core implementing a AbstractMavenLifecycleParticipant.
See https://maven.apache.org/ref/3.5.0/apidocs/org/apache/maven/AbstractMavenLifecycleParticipant.html and https://github.com/rmannibucau/maven-log-configurer-extension/blob/master/src/main/java/com/github/rmannibucau/maven/log/configurer/LogConfigurer.java for a sample. Hope it helps. Le sam. 17 août 2019 à 11:49, Paul Hammant <p...@hammant.org> a écrit : > Class > maven-core/src/main/java/org/apache/maven/project/DefaultProjectBuilder is > where "Child module <xxxxx> of <pomfile> does not exist" causes the build > to cease. I'd like to make that optional for myself for huge-monorepo and > sparse-checkout-coolness reasons. Is that the best place to make Maven > more forgiving for mussing modules in a multi-module project? > > Background: > > https://paulhammant.com/2017/02/08/further-experiments-with-expanding-contracting-monorepos/ > > - Paul >
