In this specific case, what causes the forking is the javadoc:aggregate goal. That one is meant to be used on the command line. If you want to bind it to a build phase, you should use javadoc:aggregate-no-fork. Also, javadoc:aggregate forks a "mvn compile", which will trigger the frontend:webpack (et al.) because they're bound by default to the generate-resources phase (which is odd if you ask me). You may want to bind the frontend plugin's goals to another phase, such as prepare-package.
On Tue, Dec 31, 2019 at 4:04 PM Steinar Bang <s...@dod.no> wrote: > This project https://github.com/steinarb/authservice has a lot of > messages like this in the build output: > > [INFO] > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > [INFO] Forking Authentication webapp 1.8.0-SNAPSHOT > [INFO] > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (filter-resources) @ > authservice --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] Copying 1 resource > [INFO] > [INFO] > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > [INFO] Forking Authentication webapp definitions bundle 1.8.0-SNAPSHOT > [INFO] > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (filter-resources) @ > authservice.definitions --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /home/sb/workspaces/ws03/authservice/authservice.definitions/src/main/filtered-resources > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > authservice.definitions --- > [INFO] Using 'UTF-8' encoding to copy filtered resources. > [INFO] skip non existing resourceDirectory > /home/sb/workspaces/ws03/authservice/authservice.definitions/src/main/resources > ... > > A lot of the forking messages to be repeated, so I worry that it does > some operations (e.g. the npm build of the frontend) way more times than > it has to (ie. only once). > > Is the forking something that makes the build take longer than it has > to? Or is it harmless and nothing worth spending time to fix? > > I have tried to figure out who the culprit is. Maybe there are more than > one culprit...? > > I thought maybe my use of the maven-resources-plugin in the parent was > the cause of the forking. So I moved the build of a master karaf > feature repository out of the parent POM and into a module. But that > only got rid of the first forking in the quoted text abote. > > The full output from "mvn clean install" can be seen at: > https://gist.github.com/steinarb/169d179abec47f50d3aa5574ad8d7585 > > Thanks! > > > - Steinar > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Thomas Broyer /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>
