I'm not saying you should move it, I'm only saying you have to if you don't want to build it.
The short answer my put the assembly in it's own module is that it's best practice. If your aggregating project also is the parent you may run into issues otherwise (as the parent needs to build first, but you want the assembling to happen last). There was a thread about this some days ago. Please search a mail archive (like nabble for example). /Anders On Sun, Sep 12, 2010 at 19:15, M. Richey <mric...@gmx.de> wrote: > > Hi Anders, > > when moving C outside A how to assemble B and C using the assembly plugin > and without installing the artifact before? > And why not binding the assembly plugin in project A (which is also an > aggregating project)? > > Thanks for your help! > > Regards, > > Maik > > > -------- Original-Nachricht -------- > > Datum: Sun, 12 Sep 2010 18:40:40 +0200 > > Von: Anders Hammar <and...@hammar.net> > > An: Maven Users List <users@maven.apache.org> > > Betreff: Re: [maven-assembly-plugin] Using binaries from submodule > instead of executing assembly again > > > If you execute "mvn package" on the aggregating project, all the modules > > will be built. That's how it works. If you don't want that, you need to > > move > > C outside of the aggregating project. > > You shouldn't bind the m-assembly-p in the A projects, but rather put it > > in > > a module of its own instead. That's best-practice and it will keep you > > away > > from some issues. > > > > /Anders > > > > On Sun, Sep 12, 2010 at 18:02, M. Richey <mric...@gmx.de> wrote: > > > > > Hi all, > > > > > > I've got a question regarding the assembly plugin. Assume we have three > > > projetcs called A, B, C. Project B and C are modules of A. C is a multi > > > module project itself. Both A and C uses the assembly plugin bind to > the > > > package phase. My problem is that each time executing mvn package on A > > to > > > assemble B and C together, module C is rebuild. Instead of rebuilding C > > each > > > time I would like to use the artifact attached to C (assuming that mvn > > > package has been executed on C before). Do anyone know how that can be > > done? > > > How to avoid rebuilding C again and again? Any ideas? > > > > > > Thanks in advance! > > > > > > Kind regards, > > > > > > Maik > > > > > > > > > -- > > > Achtung Sicherheitswarnung: GMX warnt vor Phishing-Attacken! > > > http://portal.gmx.net/de/go/sicherheitspaket > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > -- > GRATIS: Spider-Man 1-3 sowie 300 weitere Videos! > Jetzt freischalten! http://portal.gmx.net/de/go/maxdome > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
