On Mon, Aug 2, 2010 at 4:17 PM, Brian Fox <bri...@infinity.nu> wrote: > Your case was why I originally wrote these goals to take the artifact > info as configuration instead of from the dependency list. The only > reason you would want to use a dependency and the > copy/unpack-dependencies would be if: > You need to resolve dependencies produced by another module in the same > reactor > You're using ranges.
That is exactly my problem. Inside one aggre(g/v)ating project, I want to build module A, and then unpack it as part of setting up module B. So to ensure order I want to list A in B's dependencies ... but it does not ever belong on the classpath. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
