Dan Fabulich wrote:
Wim Deblauwe wrote:
1) You spawn a different maven process are thoses processing using
MAVEN_OPTS by default (most important would be the memory settings I have
set)?
Yes. It launches mvn with the current environment variables specified.
2) How does it know how to
Hi Dan,
seems extremely usefull to me. 2 questions I did not find an answer to in
the documentation:
1) You spawn a different maven process are thoses processing using
MAVEN_OPTS by default (most important would be the memory settings I have
set)?
2) How does it know how to stop walking up the
Wim Deblauwe wrote:
1) You spawn a different maven process are thoses processing using
MAVEN_OPTS by default (most important would be the memory settings I have
set)?
Yes. It launches mvn with the current environment variables specified.
2) How does it know how to stop walking up the
Paul Benedict wrote:
Congrats on the plugin. Could you maybe add to the plugin home page
why this plugin is required or useful? What common problem is it
trying to solve? It would be nice to know that background, because I
am grasping to find its purpose.
Which plugin home page do you mean?
The Maven team is pleased to announce the release of the Maven Reactor
Plugin, version 1.0.
This plugin can build a subset of interdependent projects in a reactor. It
should be useful in large reactor builds that include irrelevant stuff
you're not working on.
Dan,
Congrats on the plugin. Could you maybe add to the plugin home page
why this plugin is required or useful? What common problem is it
trying to solve? It would be nice to know that background, because I
am grasping to find its purpose.
Paul
