Jamie Whitehouse wrote:
Would it make more sense for the make.folders parameter to be named make.modules to keep it consistent with the same concept in multi-module builds?
I called it "folders" because you have the choice of specifying folder names or artifact names with make.artifacts.
Check out the more detailed examples here: http://maven.apache.org/plugins/maven-reactor-plugin/examples.html
Would this work with nested multi-module projects?
Yes, see the example at the end of the page linked above.
Then run at root-project: mvn reactor:make -Dmake.folders=web-services . Will this figure out that web-services, security, business-logic, mail, and preferences need to be built and do that?
Yup.
As well can these commands be invoked from within one of the modules or do they have to be run at the root-project?
They have to be run from the root project, unfortunately; that's the only place where we have enough information to construct a reactor.
-Dan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
