Maven site goal calls forks

Question

I have a supercomplex (200K java lines), a multi-module maven assembly that works fine with all the built-in modules (clean install). But when I add the target "site", I get various errors. I am talking about various errors because they go away if I build any 2 of 7 modules. I can collect even 4 of them. So I think about the race condition / order of operations like the problem - and I'm looking for asynchronous.

Then I noticed that the assembly shows such things when each module starts without a site goal:

[INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building modeul1 00-SNAPSHOT [INFO] ------------------------------------------------------------------------ ... [INFO] ------------------------------------------------------------------------ [INFO] Building modeul2 00-SNAPSHOT [INFO] ------------------------------------------------------------------------ etc... 

but for the purpose of the site, this strange replication and fork suddenly occurs:

 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building modeul1 00-SNAPSHOT [INFO] ------------------------------------------------------------------------ .... [INFO] ------------------------------------------------------------------------ [INFO] Building modeul2 00-SNAPSHOT [INFO] ------------------------------------------------------------------------ ...... [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [INFO] Forking modeul1 00-SNAPSHOT [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ... [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [INFO] Forking modeul2 00-SNAPSHOT [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ...[INFO]>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [INFO] Forking modeul1-child 00-SNAPSHOT [INFO] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> etc... 

So, my first effort is to stop the deployment (the emergence of a new JVM and a potential concurrency error) and hope this fixes my problem. But what can I do to set up a "site" target in maven so as not to create this forking behavior? Or could it be another goal referenced by the purpose of the "site", such as ...... "build"? Here is a link to it ... What is the difference between a maven building and a forking project in building multiple modules? but so far, looking at building and updating this config target in pom.xml doesn't change anything ...