cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Michels <step...@apache.org>
Subject Re: [GUMP] Build Failure - cocoon-block-fop
Date Thu, 10 Apr 2003 12:02:04 GMT


On Tue, 8 Apr 2003, Stefano Mazzocchi wrote:

> on 4/8/03 2:42 PM Stephan Michels wrote:
> >
> > On Tue, 8 Apr 2003, Stefano Mazzocchi wrote:
> >
> >>on 4/8/03 11:31 AM Gump@icarus.apache.org wrote:
> >>
> >>
> >>>fop-compile:
> >>>    [javac] Compiling 3 source files to /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030408/blocks/fop/dest
> >>>    [javac] /home/rubys/jakarta/cocoon-2.1/src/blocks/fop/java/org/apache/cocoon/serialization/FOPSerializer.java:70:
cannot resolve symbol
> >>>    [javac] symbol  : class Options
> >>>    [javac] location: package apps
> >>>    [javac] import org.apache.fop.apps.Options;
> >>>    [javac]                            ^
> >>
> >>YES! we have a dependency-clean gump run!!!!!!!!!!!!!!!!!!!!
> >>
> >>This means that from today on, if you break gump *YOU FIX IT*!!!
>
> In case you (or others) have any question, please feel free to ask.

Another question, the depend element in gump.xml declares a
dependency to another project. Does this only includes projects,
which were build by gump?

Does a 'PREREQ FAILURE - chaperon' mean that gump couldn't build
the chaperon project.

For example spark is also not a known project for gump, but the
itext block were build. So, whats the difference?

Stephan Michels.


Mime
View raw message