Any ideas? On Thu, Nov 8, 2012 at 12:40 PM, Billy Newman <[email protected]> wrote: > Almost there getting a final distribution build. I am having one last > problem that I am not sure how to solve: > > Project layout > -->module 1 (jar) > -->module 2 (war) > -->module 3 (zip) This module builds a zip archive using the assmebly plugin > --> dist module Module to create distribution > pom.xml > > My problem is that my module 3 (which is a pom artifact that creates a > zip file using the assembly plugin) is not included in my > distribution. I am guessing this is due to the module 3 pom not > really creating a maven artifact like a jar/war/ear, but instead it > creates a zip. > > Is there anyway from my child distribution pom/assembly to include the > zip archive that was created as part of the module 3 build? > > Thanks. > > On Fri, Nov 2, 2012 at 9:01 AM, Billy Newman <[email protected]> wrote: >> So I am following: >> http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html >> >> Seems pretty straight forward. I have create a child module (put it at the >> end of the module list in the parent), but I am getting this error: >> >> 'The following patterns were never triggered in this artifact inclusion >> filter >> o org.test:child1'. >> >> Been staring at this for a while and I have no idea what is wrong. >> >> I have double checked that I included the org.test:child1 artifact in the >> child distribution build. And I have also verified that I am using: >> >> <!-- Enable access to all projects in the current multimodule build! >> --> >> <useAllReactorProjects>true</useAllReactorProjects> >> >> Any ideas? >> >> Thanks, >> Billy >> >> >> >> >> On Thu, Nov 1, 2012 at 9:05 PM, Srinath C <[email protected]> wrote: >>> >>> Hi Billy, >>> >>> +1 to the way Anders suggested. >>> I had once implemented the assembling exactly the way you did, but then >>> ran >>> into issues and had to switch to having a sub-module do the assembling. >>> >>> Regards >>> Srinath. >>> >>> On Fri, Nov 2, 2012 at 6:10 AM, Wayne Fay <[email protected]> wrote: >>> >>> > > Could I get away with attaching the assembly to a different phase >>> > > (after >>> > > package) that would ensure my child modules have gone through the >>> > > package >>> > > phase. Then pull the binaries from the target dir of each child? >>> > >>> > Why would you want to? Anders told the "right" way to do this. >>> > >>> > Wayne >>> > >>> > --------------------------------------------------------------------- >>> > 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]
