> 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?
Most likely you are not using the assembly plugin correctly so the ZIP artifact is not "bound" to the build. You need to ensure the ZIP artifact in module3 is being installed into the local repo cache when you are in that project directory and type "mvn install". Also, you should be using the "single" goal of the assembly plugin. This may be important for you, from the FAQ: Can I use an artifact created by the assembly plugin as a dependency? Yes. You can refer to it using the id of the assembly as the dependency classifier. http://maven.apache.org/plugins/maven-assembly-plugin/faq.html Then you need to check how you are depending on that artifact in dist. You will need to declare <type>zip</type> in the dependency. Here's more info that may be helpful: http://www.sonatype.com/books/mvnref-book/reference/assemblies-sect-controlling-contents.html Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
