cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew C. Oliver" <acoli...@apache.org>
Subject [Proposal] All POI committers given access to POI block Re: [GUMP] Build Failure - cocoon-block-poi
Date Tue, 13 May 2003 12:04:24 GMT
Hi,

How would you guys feel about giving all POI committers CVS access to the
HSSF Serializer block?

The only downside may be granularity of CVS control, but that could be
gotten around by saying "don't commit outside of the block" to the
committers who are all reasonable nice guys.

The advantage:  While I hope around the world, they will have the ability to
fix these kinds of things.

Alternatively, I'm game to see it moved to the POI module and genericized to
be non-cocoon specific.

Thoughts? (both lists)

-Andy


On 5/11/03 4:53 AM, "Gump@icarus.apache.org" <Gump@icarus.apache.org> wrote:

> ----------------------------------------------------
> This email is autogenerated from the output from:
> <http://cvs.apache.org/builds/gump/2003-05-11/cocoon-block-poi.html>
> ----------------------------------------------------
> 
> Buildfile: build.xml
> 
> init:
> 
> init-tasks:
> 
> prepare:
>    [echo] +-----------------------------------------------------------+
>    [echo]              Apache Cocoon 20030511 [1999-2003]
>    [echo] +-----------------------------------------------------------+
>    [echo]  Building with Apache Ant version 1.6alpha compiled on May 11 2003
>    [echo]  using build file /home/rubys/jakarta/cocoon-2.1/build.xml
>    [echo]  Compiling with debug on, optimize on, deprecation off
>    [echo] +--------------------| W A R N I N G |----------------------+
>    [echo]    This build is targeted for use with JVM 1.4
>    [echo]  Using this build on a virtual machine other than the one
>    [echo]    it is targeted for may result in runtime errors.
>    [echo] +-----------------------------------------------------------+
> 
> prepare-core:
> 
> compile-core:
> 
> compile-deprecated:
> 
> prepare-blocks:
> 
> compile-tests:
> 
> gump-block:
> 
> cocoon-block-poi:
> 
> cocoon-block-poi-tests:
> 
> poi-build:
> 
> poi-prepare:
>   [mkdir] Created dir:
> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030511/blocks/poi/dest
>   [mkdir] Created dir:
> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030511/blocks/poi/conf
>    [copy] Copying 1 file to
> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030511/blocks/poi/conf
> 
> poi-mocks:
> 
> poi-compile:
>   [javac] Compiling 111 source files to
> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030511/blocks/poi/dest
>   [javac] 
> /home/rubys/jakarta/cocoon-2.1/src/blocks/poi/java/org/apache/cocoon/component
> s/elementprocessor/impl/poi/hssf/elements/EPStyle.java:208: non-static method
> getFormat(java.lang.String) cannot be referenced from a static context
>   [javac]                 short nformat =
> org.apache.poi.hssf.usermodel.HSSFDataFormat.getFormat(format);
>   [javac]        
> ^
>   [javac] 1 error
> 
> BUILD FAILED
> /home/rubys/jakarta/cocoon-2.1/build/cocoon-20030511/temp/blocks-build.xml:212
> 2: Compile failed; see the compiler error output for details.
> 
> Total time: 9 seconds
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
> 

-- 
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI

http://jakarta.apache.org/poi
For Java and Excel, Got POI?


Mime
View raw message