cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <ru...@apache.org>
Subject Re: [GUMP] Build Failure - cocoon-block-poi
Date Mon, 07 Apr 2003 12:39:45 GMT
Stefano Mazzocchi wrote:
> on 4/7/03 12:35 PM Gump@icarus.apache.org wrote:
> 
> 
>>poi-prepare:
>>    [mkdir] Created dir: /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030407/blocks/poi/dest
>>    [mkdir] Created dir: /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030407/blocks/poi/conf
>>     [copy] Copying 1 file to /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030407/blocks/poi/conf
>>
>>poi-compile:
>>    [javac] Compiling 111 source files to /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030407/blocks/poi/dest
>>    [javac] /home/rubys/jakarta/cocoon-2.1/src/blocks/poi/java/org/apache/cocoon/components/elementprocessor/impl/poi/hssf/elements/Sheet.java:62:
package org.apache.poi.hssf.usermodel does not exist
>>    [javac] import org.apache.poi.hssf.usermodel.HSSFCell;
> 
> 
> This is weird.
> 
> The cocoon-block-poi project depends on jakarta-poi, which was *NOT*
> successful last night. yet, the build of this project took process and,
> obviously, failed.
> 
> What is the problem?

Let me explain... a <depend> element indicates that one project depends 
on the jars that are produced by another project.  It is quite possible 
for a build to fail and still produce the jars - some projects produce 
web sites, javadocs, or run unit tests after they produce the jar.  In 
fact, some run the unit test before they produce the jar in order to 
prevent dependent projects from being built by gump.

In this case, the problem was that I removed a bit too much from the poi 
descriptor.  It declared no jars.

I've now corrected that.

- Sam Ruby



Mime
View raw message