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? >
