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 stop walking up the inheritance tree? What
I mean
is, why does not try to build hibernate for example (assuming my project
depends on that)? Does there need to be a parent project with a
<modules/>
section for it to work?
Yes, it requires a <modules/> section; it can only build projects
specified in your modules list. (That's what a Maven "reactor" is: a
multimodule build.)
The reactor plugin has no way to build third-party libraries like
Hibernate; it would have to pull the code down out from some remote SCM
to do that.
Would it work if I have a domain module which is used by several
applications (but is just a dependency, not part of a multimodule
build) to make that part of the chain (in either direction), if of
course the source code is available on the building pc.
Nope, a multimodule build is required here.
So, if you create an aggregation project and add the domain module and
all those dependant applications to its modules section, it should work,
shouldn't it? :-)
-Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
-------------------------------------------------------------------
GRID SYSTEMS, S.A. Rodrigo Ruiz
Parc Bit - Edificio 17 Research Coordinator
07121 Palma de Mallorca [EMAIL PROTECTED]
Baleares - Spain Tel: +34 971 435 085
http://www.gridsystems.com/ Fax: +34 971 435 082
-------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
