On Sat, Apr 12, 2014 at 8:07 AM, Hervé BOUTEMY <[email protected]> wrote: > after thinking more at it, it seems the "scope" for such artifacts is the > plugin parameter name >
I'm forking off a new thread here. A maven repository is a lovely place to keep all sorts of data used in builds: test data, templates of one sort of another. Data pushed to a repo is accessible from Maven, ant, and plain old command lines via just plain wget. However, for large objects, the Maven local repo can avoid a whole lot of time spent shoving bytes around the network. So, using 'wget' or some sort of wagon plugin is not as nice as dependency:copy or :unpack. If I'm following this thread, some people dislike this because it is our of the usual maven pattern of declaring rather than instructing: I should declare that I need a:b:1.0:zip. However, I'm failing to see the great advantage of being required to specify _both_ a dependency and then a slug of XML configuration to a plugin to specify the details of how something gets unpacked. I think that Hervé is trying to help me by suggesting that I shouldn't need the dependency: that just calling out the coordinates to something like :unpack should result in resolution via injection. Then what changes? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
