Thanks 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.
On Tue, Apr 17, 2012 at 7:25 PM, Stevo Slavić <ssla...@gmail.com> wrote: > Hello Robert, > > My guess is that the other pom defines a repository which cannot be > accessed (e.g. due to security constraints). Having failing build output, > not to mention pom files themselves, would help a lot to better diagnose > root cause. > > Regards, > Stevo. > On Apr 18, 2012 1:17 AM, "Robert Egan" <robert.e...@aciworldwide.com> > wrote: > > > I have a POM hat works correctly when it is the 'root' POM but fails to > > resolve a dependency when it is invoked as a module from another POM. > > > > How does one go about resolving an issue like this? > > >
