Hi,
AFAIK reactor can be thought of as an aggregation of the projects that
are part of the build starting from the level in the project that maven
is executed.
I think it _could_ be possible to resolve dependencies the way you
describe but it is not the way maven does it :)
-Samuli
Markus Jostock wrote:
So it's the reactor which is a kind of execution entity? I thought it
would be possible for the reactor via the parent/child relationship to
find the parent pom and therein the <module>module1</module> ...
Cheers
Markus
Samuli Saarinen wrote :
parent <-- type pom
+-- module1 <-- type jar
+-- module2 <-- type jar, depends on module 1
When you build the project from the parent level both module1 and
module2 are in the same reactor and maven is able to resolve the
dependency. That is not the case when building directly from module2
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
