You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Stephan Michels <st...@apache.org> on 2003/04/14 10:31:53 UTC

Broken cocoon build

Hi,

I tried to find the problem, which the Cocoon build currently has.
It seems to me that there is a problem with the classpath, which
the build script declares.

I'm new to gump, so, does gump handle the classpath different?
The problem is that on my local machine runs all well.

http://cvs.apache.org/builds/gump/latest/cocoon.html

I will be happy for any hints.

Thanks, Stephan Michels.

_______________________________________________________________________
         Stephan Michels               EMail: stephan@apache.org
         ICQ: 115535699                Tel: +49-030-314-21583
----+----|----+----|----+----|----+----|----+----|----+----|----+----|-|

Re: Broken cocoon build

Posted by Stephan Michels <st...@apache.org>.
On 14 Apr 2003, Stefan Bodewig wrote:

> On Mon, 14 Apr 2003, Stephan Michels <st...@apache.org> wrote:
>
> > but within the ant script, there will be also a classpath
> > declared.
>
> See <http://ant.apache.org/manual/sysclasspath.html>, Gump uses the
> "only" value.

Ahhh, yes, that explains all.

Many thanks, Stephan Michels.

Re: Broken cocoon build

Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 14 Apr 2003, Stephan Michels <st...@apache.org> wrote:

> but within the ant script, there will be also a classpath
> declared.

See <http://ant.apache.org/manual/sysclasspath.html>, Gump uses the
"only" value.

Stefan

Re: Broken cocoon build

Posted by Stephan Michels <st...@apache.org>.
On 14 Apr 2003, Stefan Bodewig wrote:

> On Mon, 14 Apr 2003, Stephan Michels <st...@apache.org> wrote:
>
> > I tried to find the problem, which the Cocoon build currently has.
> > It seems to me that there is a problem with the classpath, which
> > the build script declares.
>
> Looking at the latest run:
>
> ResolverImpl is in build/cocoon-20030414/deprecated which is not on
> your classpath, you are missing a <work> (and probably a <mkdir>)
> here.  Same for AvalonToCocoonSource.
>
> Alternatively the <work> could point to cocoon-deprecated.jar, but I'd
> strongly advise against it.  If you did so, you'd modify a jar that
> was on the CLASSPATH, which is going to either break the build (on
> Windows) or confuse the hell out of javac (the rest of the OSes).
>
> And then you seem to be missing a <depend> for XMLUnit.

Thanks, I added them to the gump descriptor. The point, I don't get,
is how gump change the classpaths for the ant scripts? I think Gump
adds the dependencies to the system classpath, but within the ant script,
there will be also a classpath declared. So why use the Ant script, which
the Gump calls, the classpath within the scripts not more. Is there
something magic :)

Stephan.

Re: Broken cocoon build

Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 14 Apr 2003, Stephan Michels <st...@apache.org> wrote:

> I tried to find the problem, which the Cocoon build currently has.
> It seems to me that there is a problem with the classpath, which
> the build script declares.

Looking at the latest run:

ResolverImpl is in build/cocoon-20030414/deprecated which is not on
your classpath, you are missing a <work> (and probably a <mkdir>)
here.  Same for AvalonToCocoonSource.

Alternatively the <work> could point to cocoon-deprecated.jar, but I'd
strongly advise against it.  If you did so, you'd modify a jar that
was on the CLASSPATH, which is going to either break the build (on
Windows) or confuse the hell out of javac (the rest of the OSes).

And then you seem to be missing a <depend> for XMLUnit.

Stefan