Hi Adam,
Adam Gibbons wrote: > > That is effectively what I have so far. Except there are also some jar > projects in the structure too which more than 1 module will reference. > (This > is to avoid sub-child modules being added to the reactor list more than > once.) So what's the problem this will result in this: root +-- pom.xml +-- m1 (j1, j2) +-- m2 (j3) +-- m3 (j1, j3) +-- m4 +-- m5 +-- j1 +-- j2 +-- j3 +-- war1 (m1,m2,m3) +-- war2 (m4) +-- war3 (m5) If you have correctly defined the dependency between the modules the build order will be done by Maven...to build this project you will go to the root and do mvn package and that should solv all things... So the point is does your current build work correctly? Have you defined the dependencies between the modules correctly? Do you have parent entry in m1..m5 etc... Adam Gibbons wrote: > At the moment I don't think the jar modules get compiled/deployed Do the modules beeing build by a single call from root ? have you tried mvn clean package ? Adam Gibbons wrote: > i'd really like to know how to achieve this! > Can I not use maven-assembly before building the war to solve the > jar/deployment issue and/or build 4 war files from 1 maven invocation? > Of course, but first you build must be working correctly... An example a single war creation you can find here: https://github.com/khmarbaise/supose/ you can enhance this by adding supplemental war-modules with appropriate dependencies. Kind regards Karl Heinz Marbaise ----- Kind regards Karl Heinz Marbaise ---- http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/The-maven-assembly-plugin-and-a-large-complex-project-tp4286366p4286443.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
