On 31/07/2011, at 11:14 AM, Mark Derricutt wrote: > I imagine a difficulty in that this would have to occur early in the > bootstrap process of maven, but if this were the case, would we not be able > to work a solution to not only the Aether inclusion issues, but also Kasun's > Gentoo resolution issues.
Replying to my own post ;-) I was just having the thought that doing something like moving the toolchains-plugin into core, and making use of this as a means to choose your dependency resolution. If we combined this idea with the discussion of a new version of the POM, we could introduce a new <toolchains/> element inside of <build/> whilst preserving backwards compatibility of declaring the toolchain plugin maybe? The superpom could declare a dependency <toolchain/> for the system default/standard resolution. And any users who want something custom would need to define it both in their pom, and there ~/.m2/toolchains.xml file - viable? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
