I have spent some time looking into the invoker plugin, and according to the specs, it is primarily used for integration testing.
My original question was whether it was possible, when invoking a maven goal on a parent POM, to force the reactor to spawn a new process for each of the submodule executions of that goal. How can I use the invoker to force the executions to fork? Assuming the invoker could be used to cause forked execution of the goal on the subprocesses, if I were to use a <preBuildHookScript>, would the execution of the script occur in the same process as the goal invocation, or would it be executed in its own process, then return to the parent process to proceed with the goal execution? Thanks ~ Tracy -----Original Message----- From: Brian Fox [mailto:[email protected]] Sent: Sunday, May 24, 2009 5:51 AM To: Maven Users List Subject: Re: Does reactor spawn a subprocess for each submodule? It runs inside the same process. You can use the invoker to fork a maven process, but this is not usually done as you describe. Why do you want to fork a new process for each module? On Fri, May 22, 2009 at 6:43 PM, Tracy Hartford <[email protected]> wrote: > I am working on a large multi-module project, and I need to know how the > reactor works when I invoke a maven goal on the parent POM. I know that > Maven adds all the submodule POMs into the Reactor, which analyzes the > dependencies between them, and determines the build order. I understand > that the Reactor then "effectively executes" the goal for each > submodule. What I need to know is, when the Reactor executes the goal > for a given submodule, does it spawn a child process to do so, or does > it execute in the current process? If it execute in the current process, > is there a way to force it to spawn a new process first? > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
