As far as I know, you can't. Maven resolves all dependencies etc at the beginning of the lifecycle, so it can find all transitive artifacts etc and make sure EVERYTHING is available in the local cache before proceeding with the build.
Wayne On 5/1/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
Here's another way of phrasing this question - if a module has a dependency on another one, how do you stop it from attempting to download until absolutely necessary (say at compile time, NOT at process-resources time)? -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 01, 2007 3:11 PM To: Maven Users List Subject: dependency management problems... We're having problems building modules like this from scratch. If we run process resources from the top most level, submodule.B complains about not being able to find module1's artifacts (why would submodule.B need module 1's jar artifact just to process resources?). parent - version 1.0-SNAPSHOT | |------->module1 - version 1.0-SNAPSHOT | |------->module2 - version 1.0-SNAPSHOT |----------->submodule.A- version 1.0-SNAPSHOT |----------->submodule.B- version 1.0-SNAPSHOT I'm really at the end of my rope on this one. The only way to successfully get this to go through is to run a mvn install from the top most level first. What's crazy is submodule.A has the same dependency and goes through just fine. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
