maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <stephen.alan.conno...@gmail.com>
Subject Re: Install hack
Date Wed, 19 Jun 2013 23:20:27 GMT
On 19 June 2013 22:31, Laird Nelson <ljnelson@gmail.com> wrote:

> On Wed, Jun 19, 2013 at 2:14 PM, Thomas Broyer <t.broyer@gmail.com> wrote:
>
> > With copy, you declare the needed artifact in the plugin configuration.
> > From Maven's PoV there's no dependency between the module that copies and
> > one being copied.
>
>
> Right.  OK.
>
>
> > That means Maven can choose to build those two modules in
> > any order.
>
>
> Sure.  Oh, I see; I would have thought this would be obvious.
>

Yes but loads of people prefer to blame maven rather than their own actions.

On re-reading that post of mine I do agree that there are a lot of layers
of information... I think the first layer does its job... and the
subtleties are there to entertain those who want to learn more about Maven


>
>
> > If copied is built before copier, all is well, copied will be
> > resolved from the reactor. However, if copier is built first, it'll pick
> > copied from the local cache (or remote repo) and won't have the proper
> > version/content (assuming SNAPSHOT, of course).
> >
>
> I see.
>
>
> > All of this us avoided with copy-dependencies, because it uses the
> module's
> > dependencies, so copier *depends* on copied and they'll always be built
> in
> > the correct order.
> >
>
> Nice; thanks for the clarification.
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message