On Apr 7, 2014, at 1:35 PM, Jörg Schaible <[email protected]> wrote:
> Jason van Zyl wrote: > >> >> I'm not exactly sure what your question is. Do you mean how would you >> accomplish these types of tasks without using the resolver directly and do >> this declaratively? > > No, the plugin should use the resolver and a user should not have to declare > such artifacts as dependencies ... just as it is now. Everything you outline really falls outside the scope of the build proper. If you trying to get artifacts for the IDE, or doing documentation and you want to then I would still limit what exactly you can see of the resolver. I think most things can be declarative, but in the cases where they truly cannot be then to extremely limit the surface area of a resolver such that the internal implementation can change without everyone being affected like they were with the Aether change. Right now I care more about the weirdness that crops up as a result of strictly build-time activities. Specifically the magic project classpath fiddling that can occur currently. > > Cheers, > Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- believe nothing, no matter where you read it, or who has said it, not even if i have said it, unless it agrees with your own reason and your own common sense. -- Buddha
