Donszelmann Mark wrote:
Is it correct that it compiles and tests fine without ever running into the install phase... That is, maven
probably sorts out that B is dependent on A, and thus in this multi-module project:
1. B does not download A,
2. B just refers to module A.
In principle yes, during a reactor build inter-module dependencies are
satisfied by the build output of the corresponding project, i.e.
"target/some.jar" or "target/classes" (if existent) in case we have no
JAR yet.
I figured out how to get all the projects in a multi-module project, and can calculate the path
to the include and libs of A, BUT it seems like maven still wants to download A before I can
do anything, so maybe my assumption was incorrect ?
It's not clear to me what your plugin does, when it does with respect to
the lifecycle and what the project setup looks like where you encounter
problems.
If your goals use @requiresDependencyResolution, this will by design
trigger resolution before your goal is invoked. Maven 3 supports an
alternative annotation @requiresDependencyCollection that allows to
determine the set of dependency artifacts without resolving their files
(MNG-4331), maybe that fits better your intentions.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
