Problem solved! Thank you Gump for finding a missing dependency! > -----Original Message----- > From: Eric Pugh [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 11, 2004 11:20 AM > To: Gump code and data > Subject: RE: Missing Class for Fulcrum DVSL > > > I have just added jaxen as an explicit maven dependency for DVSL, so > hopefully this will solve the issue. We'll see in the next run! > > I know that fixing the classloaders for plugins will break stuff, but I > believe it will be forward compatible right? If I fix a project that was > unintentionally depending on the single classloader for all > plugins, then it > will still run under maven 1.0, as well as maven 1.1? > > When you get to the point of committing the code, it may be good to put > another instance of gump up with a maven 1.1 Release Candidate so > we can see > who breaks and start fixing them before the official release of 1.1. > > Again, another good reason for Gump! > > Eric > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, November 09, 2004 10:50 PM > > To: Gump code and data > > Subject: Re: Missing Class for Fulcrum DVSL > > > > > > Just to confirm some things here: > > - test honours jar overrides as it uses maven.dependency.classpath > > - Maven does not introduce any jaxen dependencies normally. However, > > if you are using any plugin:* latka:* pmd:* release:* goals it will be > > introduced. This is an unfortunate side-effect of not having plugin > > classloaders separate - something we desparately want to implement, > > but would break a significant number of builds that have come to > > depend (no pun intended!) on it. > > > > If you run maven with -X you will see what maven.dependency.classpath > > is and whether jaxen has found its way onto there. > > > > I think Maven 1.1 is going to have to take the backwards compat hit > > and separate the classloaders. I've already done the work but not > > committed it. > > > > - Brett > > > > On Tue, 9 Nov 2004 18:55:24 +0100, Eric Pugh > > <[EMAIL PROTECTED]> wrote: > > > Not quite sure where this dependency is coming from. I don't > > believe Maven > > > is introducing for me the Jaxen dependency. As the test runs > perfectly > > > without it. Could it be the version of dom4j being used? My > > component is > > > just a wrapper around velocity-dvsl, so it may be somewhere > in there... > > > > > > I'll try and spill out the classpath in the test.. > > > > > > Eric > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, November 09, 2004 5:39 PM > > > > To: [EMAIL PROTECTED] > > > > Subject: Re: Missing Class for Fulcrum DVSL > > > > > > > > > > > > On Tue, 09 Nov 2004, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > > > > > On Tue, 9 Nov 2004, Eric Pugh <[EMAIL PROTECTED]> > > > > > wrote: > > > > > > > > >> I have inlined the text of the error. The issue is something > > > > >> missing on Jaxen. However, I have in my Gump descriptor (but not > > > > >> in Maven) a dependency on Jaxen. > > > > > > > > > > So how do you compile your code with Maven if you don't > specify the > > > > > dependency at all? Is the version of Jaxen used Maven "helping > > > > > out"? > > > > > > > > should read > > > > > > > > Is the version of Jaxen used by Maven "helping out"? > > > > > > > > Stefan > > > > > > > > > --------------------------------------------------------------------- > > > > 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] > > > > > > > > > > --------------------------------------------------------------------- > > 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] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
