The version of Mule that we are using does not use OSGi, but that should be irrelevant because the problem is occurring at compile time.
When I ran "mvn help:effective-pom," queue was still after mule and there was only one instance of each. It was quite large because it inherited a lot of dependencies from the parent project. Thanks, Brendan Haverlock -----Original Message----- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Wednesday, May 27, 2009 5:04 PM To: Maven Users List Subject: Re: Override dependency classes with another module's classes > So the module "A" that has these 2 dependencies is trying to use the > implementations from the queue-override that overrides the packages/classes > inside of mule. So: Is Mule perhaps using OSGi or something to look up classes, so even though your artifacts/classes appear first in the classpath, they are getting ignored? What does "mvn help:effective-pom" show you? I'm not entirely convinced this is Maven performing badly but rather something more intricate going on... Might want to take this over to the Mule list to see what people there think. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org