Because of the comment here. I have never been able to get my project to build properly if I attach my assembly as a build step.
http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html <http://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html> *NOTE:* Because of a quirk in Maven 2.0's execution model relating to aggregator mojos and the inheritance hierarchy, we need to explicitly execute the package phase ahead of the assembly invocation, to ensure all modules have been built. I would prefer to build the entire project from one command line. If I put the assembly into a sub project that is two steps. I must install all of my artifacts and then run assembly on another module. While feasible it seems wrong to me that I can't simply walk up to the top level and build my entire maven project using a single command line. Again, my project builds fine. if I do mvn package from the top level. However things only go awry when using the assembly plugin. On Tue, Jan 19, 2010 at 3:00 PM, Wayne Fay <[email protected]> wrote: > > 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. > > Why not?? "I don't want to" is not a valid answer. Maven uses its > repository for a lot of things, you need to get comfortable using it. > > Is there a reason you're specifying assembly:assembly from the command > line instead of simply binding it in your pom? > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
