Best-practice. Here's one reason: http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#module-binaries
/Anders On Thu, Sep 2, 2010 at 20:54, Pulkit Singhal <[email protected]>wrote: > Do you mean structuring it like so: > > parent-maven-project > |__childA-maven-project > |__childB-maven-project > |__childC-maven-project > |__fake-assembly-project > > Is that the best-practice or the practical-practice? > > I ask because it feels a bit odd to have a parent for modules and then > not use it for something like assembling the structure for the final > releasable product based on the artifacts from its children. > > On Thu, Sep 2, 2010 at 2:43 PM, Wendy Smoak <[email protected]> wrote: > > On Thu, Sep 2, 2010 at 1:26 PM, Pulkit Singhal <[email protected]> > wrote: > >> In a multi-module project, I am attempting to provide the parent pom > >> with an assembly descriptor which will pick up the artifacts from some > >> of its children modules > > > > This works best if you put the assembly in its own module, not in the > parent. > > > > -- > > Wendy > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
