You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Henning Schmiedehausen <hp...@intermeta.de> on 2005/10/30 21:58:14 UTC
Current failure of "jakarta-velocity-test"
Hi,
(I'm not a gump person, so please bear with me). Currently the vmgump
fails as shown on
http://vmgump.apache.org/gump/public/jakarta-velocity/jakarta-velocity-test/index.html
in the jakarta-velocity-test module and I don't understand why. Is gump
somehow overriding the ant classpath? The failing test relies on ant
putting a certain jar on the classpath so that a (classpath based)
loader can find a template. This does not work (see
http://vmgump.apache.org/gump/public/jakarta-velocity/jakarta-velocity-
test/gump_work/build_jakarta-velocity_jakarta-velocity-test.html)
This works fine when running the tests standalone (get the velocity
distribution, do "cd build, ant test").
I can't readily see how we can fix this gump failure short of removing
the tests from the gump build.
Advise very welcome. Please keep me on the Cc because I'm not subscribed
to general@gump.
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development
Linux, Java, perl, Solaris -- Consulting, Training, Engineering
4 - 8 - 15 - 16 - 23 - 42
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: Current failure of "jakarta-velocity-test"
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Thanks,
I've put a fix into the jakarta-velocity project, I'm looking forward to
see how it works out.
Best regards
Henning
On Sun, 2005-10-30 at 22:30 +0100, Stefan Bodewig wrote:
> On Sun, 30 Oct 2005, Henning Schmiedehausen <hp...@intermeta.de> wrote:
>
> > Is gump somehow overriding the ant classpath?
>
> Yes, more than that actually. It sets the magic build.sysclasspath
> property to only which makes Ant ignore any classpath setting inside
> the build file and only take into account what the system classpath
> holds.
>
> > The failing test relies on ant putting a certain jar on the
> > classpath so that a (classpath based) loader can find a
> > template.
>
> Where is this template - or the jar? In gump's descriptor for
> velocity-test you "simply" add a <work> entry that points to it.
> <work> adds whatever the "nested" attribute holds to CLASSPATH prior
> to running Ant.
>
> Cheers
>
> Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: Current failure of "jakarta-velocity-test"
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Thanks,
I've put a fix into the jakarta-velocity project, I'm looking forward to
see how it works out.
Best regards
Henning
On Sun, 2005-10-30 at 22:30 +0100, Stefan Bodewig wrote:
> On Sun, 30 Oct 2005, Henning Schmiedehausen <hp...@intermeta.de> wrote:
>
> > Is gump somehow overriding the ant classpath?
>
> Yes, more than that actually. It sets the magic build.sysclasspath
> property to only which makes Ant ignore any classpath setting inside
> the build file and only take into account what the system classpath
> holds.
>
> > The failing test relies on ant putting a certain jar on the
> > classpath so that a (classpath based) loader can find a
> > template.
>
> Where is this template - or the jar? In gump's descriptor for
> velocity-test you "simply" add a <work> entry that points to it.
> <work> adds whatever the "nested" attribute holds to CLASSPATH prior
> to running Ant.
>
> Cheers
>
> Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Current failure of "jakarta-velocity-test"
Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 30 Oct 2005, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> Is gump somehow overriding the ant classpath?
Yes, more than that actually. It sets the magic build.sysclasspath
property to only which makes Ant ignore any classpath setting inside
the build file and only take into account what the system classpath
holds.
> The failing test relies on ant putting a certain jar on the
> classpath so that a (classpath based) loader can find a
> template.
Where is this template - or the jar? In gump's descriptor for
velocity-test you "simply" add a <work> entry that points to it.
<work> adds whatever the "nested" attribute holds to CLASSPATH prior
to running Ant.
Cheers
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: Current failure of "jakarta-velocity-test"
Posted by Stefan Bodewig <bo...@apache.org>.
On Sun, 30 Oct 2005, Henning Schmiedehausen <hp...@intermeta.de> wrote:
> Is gump somehow overriding the ant classpath?
Yes, more than that actually. It sets the magic build.sysclasspath
property to only which makes Ant ignore any classpath setting inside
the build file and only take into account what the system classpath
holds.
> The failing test relies on ant putting a certain jar on the
> classpath so that a (classpath based) loader can find a
> template.
Where is this template - or the jar? In gump's descriptor for
velocity-test you "simply" add a <work> entry that points to it.
<work> adds whatever the "nested" attribute holds to CLASSPATH prior
to running Ant.
Cheers
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org