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 <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > >
