You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Eric Pugh <ep...@opensourceconnections.com> on 2004/11/09 15:55:24 UTC
Missing Class for Fulcrum DVSL
Well,
The second to last build issue for Fulcrum concerns Fulcrum DVSL Impl.
Everything builds nicely, but the unit test is failing:
http://brutus.apache.org/gump/public/jakarta-turbine-fulcrum/fulcrum-dvsl-im
pl/gump_work/build_jakarta-turbine-fulcrum_fulcrum-dvsl-impl.html
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.
I notice in the jaxen.xml project file there are two different ones. A
packaged with dom4j and a standalone. Do I maybe want the packaged with
dom4j?
I went and checked, and org.jaxen.JaxenException is still part of CVS HEAD
for jaxen...
ERic
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Missing Class for Fulcrum DVSL
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 10 Nov 2004, Brett Porter <br...@gmail.com> wrote:
> - test honours jar overrides as it uses maven.dependency.classpath
> - Maven does not introduce any jaxen dependencies normally.
Thanks for the clarification
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: Missing Class for Fulcrum DVSL
Posted by Eric Pugh <ep...@opensourceconnections.com>.
Problem solved! Thank you Gump for finding a missing dependency!
> -----Original Message-----
> From: Eric Pugh [mailto:epugh@opensourceconnections.com]
> 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:brett.porter@gmail.com]
> > 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
> > <ep...@opensourceconnections.com> 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:bodewig@apache.org]
> > > > Sent: Tuesday, November 09, 2004 5:39 PM
> > > > To: general@gump.apache.org
> > > > Subject: Re: Missing Class for Fulcrum DVSL
> > > >
> > > >
> > > > On Tue, 09 Nov 2004, Stefan Bodewig <bo...@apache.org> wrote:
> > > > > On Tue, 9 Nov 2004, Eric Pugh <ep...@opensourceconnections.com>
> > > > > 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: general-unsubscribe@gump.apache.org
> > > > For additional commands, e-mail: general-help@gump.apache.org
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> > > For additional commands, e-mail: general-help@gump.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> > For additional commands, e-mail: general-help@gump.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: Missing Class for Fulcrum DVSL
Posted by Eric Pugh <ep...@opensourceconnections.com>.
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:brett.porter@gmail.com]
> 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
> <ep...@opensourceconnections.com> 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:bodewig@apache.org]
> > > Sent: Tuesday, November 09, 2004 5:39 PM
> > > To: general@gump.apache.org
> > > Subject: Re: Missing Class for Fulcrum DVSL
> > >
> > >
> > > On Tue, 09 Nov 2004, Stefan Bodewig <bo...@apache.org> wrote:
> > > > On Tue, 9 Nov 2004, Eric Pugh <ep...@opensourceconnections.com>
> > > > 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: general-unsubscribe@gump.apache.org
> > > For additional commands, e-mail: general-help@gump.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> > For additional commands, e-mail: general-help@gump.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Missing Class for Fulcrum DVSL
Posted by Brett Porter <br...@gmail.com>.
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
<ep...@opensourceconnections.com> 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:bodewig@apache.org]
> > Sent: Tuesday, November 09, 2004 5:39 PM
> > To: general@gump.apache.org
> > Subject: Re: Missing Class for Fulcrum DVSL
> >
> >
> > On Tue, 09 Nov 2004, Stefan Bodewig <bo...@apache.org> wrote:
> > > On Tue, 9 Nov 2004, Eric Pugh <ep...@opensourceconnections.com>
> > > 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: general-unsubscribe@gump.apache.org
> > For additional commands, e-mail: general-help@gump.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Missing Class for Fulcrum DVSL
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 9 Nov 2004, Eric Pugh <ep...@opensourceconnections.com> 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?
Quite possible.
So if you build with Maven you use an older version of dom4j that
doesn't need Jaxen at runtime while dom4j's CVS HEAD does. Sounds
likely.
Brett, if project.xml doesn't contain any reference to Jaxen but
jaxen.jar happens to be on the system CLASSPATH, will a test run by
Maven see Jaxen?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
RE: Missing Class for Fulcrum DVSL
Posted by Eric Pugh <ep...@opensourceconnections.com>.
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:bodewig@apache.org]
> Sent: Tuesday, November 09, 2004 5:39 PM
> To: general@gump.apache.org
> Subject: Re: Missing Class for Fulcrum DVSL
>
>
> On Tue, 09 Nov 2004, Stefan Bodewig <bo...@apache.org> wrote:
> > On Tue, 9 Nov 2004, Eric Pugh <ep...@opensourceconnections.com>
> > 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: general-unsubscribe@gump.apache.org
> For additional commands, e-mail: general-help@gump.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Missing Class for Fulcrum DVSL
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 09 Nov 2004, Stefan Bodewig <bo...@apache.org> wrote:
> On Tue, 9 Nov 2004, Eric Pugh <ep...@opensourceconnections.com>
> 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: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Missing Class for Fulcrum DVSL
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 9 Nov 2004, Eric Pugh <ep...@opensourceconnections.com> wrote:
> The second to last build issue for Fulcrum concerns Fulcrum DVSL
> Impl. Everything builds nicely, but the unit test is failing:
I'm not completely certain that Maven's test plugin (is that the
correct term?) honors jar overrides, so I'm not completely sure which
classpath your tests see.
Could you echo out java.class.path inside of your tests to see what is
going on.
> 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"?
This scares me more than a bit.
> I notice in the jaxen.xml project file there are two different ones.
> A packaged with dom4j and a standalone. Do I maybe want the
> packaged with dom4j?
This is in order to break a cyclic dependency between jaxen and
dom4j. The resulting jars should work the same way, but only "jaxen"
has been compiled against the same dom4j version you use, so you
probably want to use that.
> I went and checked, and org.jaxen.JaxenException is still part of
> CVS HEAD for jaxen...
IIRC it has changed its parent class, though. Saxpath moved around a
bit.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org