This is pretty messed up. If I build the harness locally, it works ok. I moved some of the stubs from mdep up to the harness, built and redeployed the harness snapshot. All is fine in mdep. Then when maven decides the snapshot I deployed is newer than the one in my local repo, suddenly the tests start failing again. Install harness again locally and they work. Somehow the fact that it comes from the remote repo seems to affect the classpath ordering.
-----Original Message----- From: Mark Hobson [mailto:[EMAIL PROTECTED] Sent: Friday, June 22, 2007 12:45 PM To: Maven Developers List Subject: Re: maven-dependency-plugin tests failing On 22/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > On 22/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > > On 21/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote: > > > On 21/06/07, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > > > That's odd, I am able to build mdep with no problems. > > > > > > I'm building using the current 2.0.x branch, if that makes any difference? > > > > Same problem with 2.0.5, 2.0.6 and 2.0.7.. > > Okay, after a bit of digging, it appears to be due to two versions of > PlexusContainer being in the classpath. They're coming from: > > - plexus-component-api-1.0-alpha-15.jar > - plexus-container-default-1.0-alpha-9-stable-1.jar > > The first jar defines PlexusContainer without an initialize() method, > whereas the second jar does. Thus for all PlexusTestCases this > results in: > > java.lang.NoSuchMethodError: org.codehaus.plexus.PlexusContainer.initialize()V > > Anyone have any insight into these differing PlexusContainer APIs and > how one should resolve them? Looks like PlexusContainer was moved from plexus-container-default to plexus-component-api sometime between 1.0-alpha-9 and 1.0-alpha-15. It's the plexus-archiver 1.0-alpha-9-SNAPSHOT dependency that is bringing in conflicting versions. I guess all the plexus dependencies need to be aligned to the same API version. Oh for some dependency diagnostic tools.. ;) Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
