I wonder…
When using a fully integrated source tree (parent poms and all that,
checked out from subversion in one fell swoop), sometimes I
reflexively jump into a subdirectory and get burned when Maven goes
out to the repository to download deployed versions of my projects
under development. For instance, given this tree:
parent/ { packaging: pom }
module1/ { packaging: war, dependency: module2 }
module2/ { packaging: jar }
module3/ { packaging: jar }
It would be nice to be able to:
cd parent/module1
mvn test
And build module1 and module2 without looking for module2 in the
repository when it's sitting right nearby. Of course, this should
only happen if ../pom.xml is pom.xml's parent (and recursively so-
forth).
I'm sure this is nontrivial, but am I nuts? Is there a scenario where
the current behavior is desirable?
— G
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
