I have uploaded a second copy of my project http://weseewhathappens.com/mvn2.zip
I took your suggestion and create a second module called assembly. And moved the assembly plugin there. I also added my other jars as dependencies. At the top level if I run mvn package, things work fine as expected. if I run mvn package assembly:assembly I get [INFO] Error reading assemblies: No assembly descriptors found. I assume this is because I have no assembly at the top level. Since I am not installing the jar-a -> jar-b in the local repo I can't run assembly on the sub module as I will get errors regarding missing dependencies. On Tue, Jan 19, 2010 at 1:09 PM, Bill Smith <ne...@weseewhathappens.com>wrote: > Woult this new module for the assembly be a jar module or a pom only > module? > > > On Mon, Jan 18, 2010 at 9:38 PM, Wayne Fay <wayne...@gmail.com> wrote: > >> > I think what you are suggesting is rather then have a parent module to >> have >> > another module at the same level as the jar/wars and list them as actual >> > dependencies? >> >> Yes. The parent will be merely a "pom" project with no assembly plugin >> declared, and then you'll have another module under it that is simply >> your assembly project which lists the other modules as dependencies. >> >> You can read more about assemblies in the Sonatype book "Maven the >> definitive guide" free online, especially section 8.6.2: >> http://www.sonatype.com/books/mvnref-book/reference/assemblies.html >> >> Wayne >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >
