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?
On Sun, May 24, 2009 at 14:50, Brian Fox <[email protected]> wrote: > 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? One might do so hoping to allow builds to run in parallel on a multi-core machine. Not that there'd be much point since maven's local .m2/repository is not safe for concurrent access: http://jira.codehaus.org/browse/MNG-3004 // ben --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
