I don't understand the remark about M3. Either it implies that it \won't/ work in M2, or perhaps you left out a word?
On Wed, Aug 4, 2010 at 7:26 PM, Brian Fox <[email protected]> wrote: > In that case you'll need to use the unpack-dependencies goal along > with provided. It's possible that this would work correctly in M3 > though because of the rework in the resolution. > > On Mon, Aug 2, 2010 at 9:18 PM, Benson Margulies <[email protected]> > wrote: >> On Mon, Aug 2, 2010 at 4:17 PM, Brian Fox <[email protected]> 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: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > 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]
