Thanks Mantas, I think I figured it out. There's nothing wrong with the structure of my reactor.
If I build a reactor with 1 thread, the projects are built in order from A to Z and there's no way a project could not get built. Now suppose I introduce some bugs into the code and build again with 3 threads (no pom files have changed). The build fails on project M, and the message says to rerun and resume from project M. I do that, and then it fails again on project X. If I resume from project X, the build might end with Z successfully. But it's possible that project P was never built. I suspect this is what is happening. It seems when --resume-from is used together with --threads, there can be some confusion as to what is built. This isn't mentioned in http://maven.apache.org/guides/mini/guide-multiple-modules.html or http://maven.apache.org/guides/mini/guide-multiple-modules-4.html Delany On Thu, 25 Nov 2021 at 11:36, Mantas Gridinas <mgridi...@gmail.com> wrote: > If you're working with maven 3 you can check the miniguide "Guide to > Woeking with multiple modules". Reactor should sort out your modules in > such way that dependency modules are built earlier in the reactor but in my > experience they would get skipped if you use resume flag. The guide > suggests that you could try including also-make and also-make-dependents to > ensure that modules get rebuilt both ways when you rebuild a particular > module. > > My advice is to look through your module declaration order and fix your > poms to not depend on modules that appear later in the build process. That > way you won't depend on reactor figuring out the order for you and reduce > possible headaches in the future. > > On Thu, Nov 25, 2021, 11:22 Delany <delany.middle...@gmail.com> wrote: > > > Hi. How does --resume-from actually work? Is there any information cached > > between builds somewhere? > > I made some sweeping changes to a 500+ modules reactor. As I fix the > build > > errors in each project, I use -rf to continue without restarting each > time. > > I finally get to the end of the build thinking I've fixed all the errors, > > but when I run the build again from the beginning new ones pop up. > > > > Thanks, > > >
