Thanks But that's not my decision to make.
On Tue, Apr 17, 2012 at 9:38 PM, Wayne Fay <wayne...@gmail.com> wrote: > > The real answer is that in the multi-module project, someone calls the > > 'standard' assembly plugin before I do (there are many other EARs, WARs > and > > JARs in the build). So it is the one in memory when the module that needs > > mine is invoked. I need to find a way to insure that my assembly plugin > is > > loaded first, and therefore loads the required dependency. > > Or you could just move to Maven3 where this bug in M2 was resolved... > assuming that I understand what you are saying. Otherwise if you are > on M3, you need to adjust your dependencies and declare things in such > a way that Maven can properly calculate the build path. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
