Actually, I should clarify: ProjectConsumingWebService does NOT fail to resolve the dependency - at least, Maven doesn't complain that it can't find it - but it is not adding it to the build path, because I get compilation errors related to missing classes that are in the client classifier.
On 10/2/07, Dave Feltenberger <[EMAIL PROTECTED]> wrote: > All - > > I have a multi-module build (maybe 15 modules in all), and one of the > projects is failing to resolve a dependency on an artifact with a > classifier. > > WebServiceProject > - WAR artifact > - client stubs (using a classifier) > > ProjectConsumingWebService > - depends on WebServiceProject-client > > When I do a build of the entire project, ProjectConsumingWebService is > failing to resolve the client dependency. But when I run a bulid of > *only* the ProjectConsumingWebService, it works fine. > > Anyone have any ideas? > > I've seen this bug: > http://jira.codehaus.org/browse/MECLIPSE-287 > > But it appears to be specific to the Eclipse Plugin. > > Thanks. > > Dave > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
