On Thu, Sep 2, 2010 at 2:54 PM, 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.
Search the archives and JIRA for more info, but in brief there's a problem because the parent has to build first so it's available for the children, yet the assembly needs to build last because it needs the artifacts from the children. Your life will be much easier if you make the assembly a module of its own. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
