You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by "Andrew C. Oliver" <ac...@apache.org> on 2003/05/13 14:04:24 UTC
[Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
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" <Gu...@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?
Re: [Proposal] All POI committers given access to POI block Re: [GUMP]
Build Failure - cocoon-block-poi
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Bruno Dumon wrote, On 13/05/2003 15.10:
> On Tue, 2003-05-13 at 14:04, Andrew C. Oliver wrote:
...
>>Alternatively, I'm game to see it moved to the POI module and genericized to
>>be non-cocoon specific.
>
> +1 to move the code to POI.
+1 here
> (there are some patches for the serializer waiting in bugzilla -- don't
> forget those)
>
> BTW, what happened to morphos?
I removed it from Jakarta Commons - too much traffic for me now and also
Andy does not want to help there because of it, and are moving it to SF.
I proposed Cocoon that I work on it @ Cocoon, but had only negative
responses AFAIK. I'd be happy to work on it here in the scratchpad, but
only if others want.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by Bruno Dumon <br...@outerthought.org>.
On Tue, 2003-05-13 at 14:04, Andrew C. Oliver wrote:
> 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.
+1 to move the code to POI.
(there are some patches for the serializer waiting in bugzilla -- don't
forget those)
BTW, what happened to morphos?
--
Bruno Dumon http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org bruno@apache.org
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by "Andrew C. Oliver" <ac...@apache.org>.
And DO note that by the end I'd changed my mind and so had you. Leaving us
on opposite sides! Anyhow, bygones.
-Andy
On 5/13/03 8:10 AM, "Sylvain Wallez" <sy...@anyware-tech.com>
wrote:
> Andrew C. Oliver wrote:
>
>> Agreed.
>>
>
> Mee too, more than one year ago ;-)
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=101550014508306&w=2
>
>> On 5/13/03 7:41 AM, "Csaba Nagy" <na...@ecircle-ag.com> wrote:
>>
>>
>>> I'm not a committer, just a user of POI (in a fairly simple scenario), but
>>> at one time I was looking into using the HSSF serializer, only it was
>>> married with cocoon, which I had no intention to use. So I didn't use it.
>>> My personal opinion is that the serializer belongs to POI, any other project
>>> should use an adapter of some sort.
>>>
>>> Cheers,
>>> Csaba.
>>>
>>>
>>>
--
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?
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by "Andrew C. Oliver" <ac...@apache.org>.
And DO note that by the end I'd changed my mind and so had you. Leaving us
on opposite sides! Anyhow, bygones.
-Andy
On 5/13/03 8:10 AM, "Sylvain Wallez" <sy...@anyware-tech.com>
wrote:
> Andrew C. Oliver wrote:
>
>> Agreed.
>>
>
> Mee too, more than one year ago ;-)
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=101550014508306&w=2
>
>> On 5/13/03 7:41 AM, "Csaba Nagy" <na...@ecircle-ag.com> wrote:
>>
>>
>>> I'm not a committer, just a user of POI (in a fairly simple scenario), but
>>> at one time I was looking into using the HSSF serializer, only it was
>>> married with cocoon, which I had no intention to use. So I didn't use it.
>>> My personal opinion is that the serializer belongs to POI, any other project
>>> should use an adapter of some sort.
>>>
>>> Cheers,
>>> Csaba.
>>>
>>>
>>>
--
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?
Re: [Proposal] All POI committers given access to POI block Re: [GUMP]
Build Failure - cocoon-block-poi
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Andrew C. Oliver wrote:
>Agreed.
>
Mee too, more than one year ago ;-)
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=101550014508306&w=2
>On 5/13/03 7:41 AM, "Csaba Nagy" <na...@ecircle-ag.com> wrote:
>
>
>>I'm not a committer, just a user of POI (in a fairly simple scenario), but at one time I was looking into using the HSSF serializer, only it was married with cocoon, which I had no intention to use. So I didn't use it.
>>My personal opinion is that the serializer belongs to POI, any other project should use an adapter of some sort.
>>
>>Cheers,
>>Csaba.
>>
>>
>>
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Agreed.
On 5/13/03 7:41 AM, "Csaba Nagy" <na...@ecircle-ag.com> wrote:
> I'm not a committer, just a user of POI (in a fairly simple scenario),
> but at one time I was looking into using the HSSF serializer, only it
> was married with cocoon, which I had no intention to use. So I didn't
> use it.
> My personal opinion is that the serializer belongs to POI, any other
> project should use an adapter of some sort.
>
> Cheers,
> Csaba.
>
> On Tue, 2003-05-13 at 14:04, Andrew C. Oliver wrote:
>> 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" <Gu...@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/compone
>>> nt
>>> 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:2
>>> 12
>>> 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?
>>
>>
>> ---------------------------------------------------------------------
>> 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?
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Agreed.
On 5/13/03 7:41 AM, "Csaba Nagy" <na...@ecircle-ag.com> wrote:
> I'm not a committer, just a user of POI (in a fairly simple scenario),
> but at one time I was looking into using the HSSF serializer, only it
> was married with cocoon, which I had no intention to use. So I didn't
> use it.
> My personal opinion is that the serializer belongs to POI, any other
> project should use an adapter of some sort.
>
> Cheers,
> Csaba.
>
> On Tue, 2003-05-13 at 14:04, Andrew C. Oliver wrote:
>> 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" <Gu...@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/compone
>>> nt
>>> 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:2
>>> 12
>>> 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?
>>
>>
>> ---------------------------------------------------------------------
>> 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?
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by Csaba Nagy <na...@ecircle-ag.com>.
I'm not a committer, just a user of POI (in a fairly simple scenario),
but at one time I was looking into using the HSSF serializer, only it
was married with cocoon, which I had no intention to use. So I didn't
use it.
My personal opinion is that the serializer belongs to POI, any other
project should use an adapter of some sort.
Cheers,
Csaba.
On Tue, 2003-05-13 at 14:04, Andrew C. Oliver wrote:
> 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" <Gu...@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?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Then its silly to have Gump work. If "dev" versions count, fine, but I'll
request that the block failures don't go to the poi-dev list as they'll be
silly and frivolous. Wish I'd not been swamped. I'd have voted -1 in a
heartbeat. I'm not an XP-er strictly but I'm sure as heck not a SDLCiac
either.
So it doesn't work at all, not now, not ever. (This isn't intended to be
flame bait just factual analysis :-) )
-andy
>
> Here is an issue: some time ago we decided to use in Cocoon CVS only
> released versions of the libraries. Meaning, once you change POI APIs in
> backward incompatible way, you first need to make a release and then it
> can be put into Cocoon. (How) Will this work for you?
>
> Vadim
>
>
>> -Andy
>>
>>
>> On 5/11/03 4:53 AM, "Gump@icarus.apache.org" <Gu...@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>
>>> ----------------------------------------------------
>>>
>>>
> ...
>
>
--
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?
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Then its silly to have Gump work. If "dev" versions count, fine, but I'll
request that the block failures don't go to the poi-dev list as they'll be
silly and frivolous. Wish I'd not been swamped. I'd have voted -1 in a
heartbeat. I'm not an XP-er strictly but I'm sure as heck not a SDLCiac
either.
So it doesn't work at all, not now, not ever. (This isn't intended to be
flame bait just factual analysis :-) )
-andy
>
> Here is an issue: some time ago we decided to use in Cocoon CVS only
> released versions of the libraries. Meaning, once you change POI APIs in
> backward incompatible way, you first need to make a release and then it
> can be put into Cocoon. (How) Will this work for you?
>
> Vadim
>
>
>> -Andy
>>
>>
>> On 5/11/03 4:53 AM, "Gump@icarus.apache.org" <Gu...@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>
>>> ----------------------------------------------------
>>>
>>>
> ...
>
>
--
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?
Re: [Proposal] All POI committers given access to POI block Re: [GUMP]
Build Failure - cocoon-block-poi
Posted by Vadim Gritsenko <va...@verizon.net>.
Andrew C. Oliver wrote:
>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)
>
>
Here is an issue: some time ago we decided to use in Cocoon CVS only
released versions of the libraries. Meaning, once you change POI APIs in
backward incompatible way, you first need to make a release and then it
can be put into Cocoon. (How) Will this work for you?
Vadim
>-Andy
>
>
>On 5/11/03 4:53 AM, "Gump@icarus.apache.org" <Gu...@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>
>>----------------------------------------------------
>>
>>
...
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by "Andrew C. Oliver" <ac...@apache.org>.
No no.. This isn't going to just be Cocoon based anymore. This is an
XML-> Excel translation layer. And it will soon be an Excel -> XML
translation layer as well. Forget about Cocoon in this context. Cocoon
will presumably use it in a very lightweight class but you'll easily be able
to run it WITHOUT cocoon.
So You know XML. You know HSSF, this is the two of them together :-)
Secret sauce.
On 5/14/03 7:56 AM, "Glen Stampoultzis" <gs...@iinet.net.au> wrote:
> At 11:11 AM 14/05/2003, you wrote:
>> POI Folks please vote on accepting this:
>>
>> [ ] +1
>> [X] +0 I have no coocon knowledge but I'm not against it.
>> [ ] -0
>> [ ] -1
>
>
> Glen Stampoultzis
> gstamp@iinet.net.au
> http://members.iinet.net.au/~gstamp/glen/
>
--
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?
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Glen Stampoultzis <gs...@iinet.net.au>.
At 11:11 AM 14/05/2003, you wrote:
>POI Folks please vote on accepting this:
>
>[ ] +1
>[X] +0 I have no coocon knowledge but I'm not against it.
>[ ] -0
>[ ] -1
Glen Stampoultzis
gstamp@iinet.net.au
http://members.iinet.net.au/~gstamp/glen/
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 13.May.2003 -- 08:11 PM, Andrew C. Oliver wrote:
> Cocoon folks please vote:
>
[X] +1
> [ ] +0
> [ ] -0
> [ ] -1
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Stefano Mazzocchi <st...@apache.org>.
on 5/14/03 2:48 AM Sylvain Wallez wrote:
> Andrew C. Oliver wrote:
>
>
>>Cocoon folks please vote:
>>
>>[X] +1
>>[ ] +0
>>[ ] -0
>>[ ] -1
>>
>>
+1 to Andy's proposition
and +1 to Vadim's corrections (even if I think this is was Andy meant in
the first place)
--
Stefano.
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Andrew C. Oliver wrote:
>Cocoon folks please vote:
>
>[X] +1
>[ ] +0
>[ ] -0
>[ ] -1
>
>
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Rainer Klute <ra...@gmx.de>.
> POI Folks please vote on accepting this:
>
> [ ] +1
> [X] +0
> [ ] -0
> [ ] -1
Best regards
Rainer Klute
--
RAINER KLUTE IT-CONSULTING GMBH
Dipl.-Inform.
Rainer Klute klute@rainer-klute.de
Körner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Rainer Klute <ra...@gmx.de>.
> POI Folks please vote on accepting this:
>
> [ ] +1
> [X] +0
> [ ] -0
> [ ] -1
Best regards
Rainer Klute
--
RAINER KLUTE IT-CONSULTING GMBH
Dipl.-Inform.
Rainer Klute klute@rainer-klute.de
Körner Grund 24 Telefon: +49 172 2324824
D-44143 Dortmund Telefax: +49 231 5349423
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte lächeln! Fotogalerie online mit GMX ohne eigene Homepage!
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Giacomo Pati <gi...@apache.org>.
On Tue, 13 May 2003, Andrew C. Oliver wrote:
> Cocoon folks please vote:
>
> [X] +1
> [ ] +0
> [ ] -0
> [ ] -1
Giacomo
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by David Crossley <cr...@indexgeo.com.au>.
(Note: removed Cc to Stefano - he is on cocoon-dev.)
Andrew C. Oliver wrote:
> Cocoon folks please vote:
>
> [X] +1
> [ ] +0
> [ ] -0
> [ ] -1
>
> POI Folks please vote on accepting this:
>
> [ ] +1
> [ ] +0
> [ ] -0
> [ ] -1
>
> For explanations read below. I'm too tired to recite it all and be fancy.
>
> -Andy
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Andrew Savory <an...@luminas.co.uk>.
On Tue, 13 May 2003, Andrew C. Oliver wrote:
> Cocoon folks please vote:
>
> [X] +1
> [ ] +0
> [ ] -0
> [ ] -1
Andrew.
--
Andrew Savory Email: andrew@luminas.co.uk
Managing Director Tel: +44 (0)870 741 6658
Luminas Internet Applications Fax: +44 (0)700 598 1135
This is not an official statement or order. Web: www.luminas.co.uk
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Ryan Ackley <sa...@cfl.rr.com>.
[X] +1
[ ] +0
[ ] -0
[ ] -1
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Danny Mui <da...@muibros.com>.
XML is a very tasty secret sauce!
>POI Folks please vote on accepting this:
>
>[X] +1
>[ ] +0
>[ ] -0
>[ ] -1
>
>
>
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Joerg Heinicke <jo...@gmx.de>.
Andrew C. Oliver wrote:
> Cocoon folks please vote:
>
> [X] +1
> [ ] +0
> [ ] -0
> [ ] -1
Joerg
--
System Development
VIRBUS AG
Fon +49(0)341-979-7419
Fax +49(0)341-979-7409
joerg.heinicke@virbus.de
www.virbus.de
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Torsten Curdt <tc...@dff.st>.
+1
and
+1
--
Torsten
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Steven Noels wrote, On 14/05/2003 7.19:
> On 14/05/2003 5:02 Vadim Gritsenko wrote:
>
>>> Cocoon folks please vote:
>>>
[x] +1
>>> [ ] +0
>>> [ ] -0
>>> [ ] -1
>>
>>
>> I presume you mean ms excel serialization classes. Block itself will
>> still be here and will include jar from POI with serialization classes
>> as well as samples.
>
> double +1
double +1 here too
I don't think Andy whats cocoon.jar in the list of Cocoon dependencies,
no? ;-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Steven Noels <st...@outerthought.org>.
On 14/05/2003 5:02 Vadim Gritsenko wrote:
>> Cocoon folks please vote:
>>
>> [x] +1
>> [ ] +0
>> [ ] -0
>> [ ] -1
>>
>
> I presume you mean ms excel serialization classes. Block itself will
> still be here and will include jar from POI with serialization classes
> as well as samples.
double +1
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
RE: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Geoff Howard <co...@leverageweb.com>.
+1
>
> Has anyone written an HSSFGenerator? I wrote an HSSFTransformer... Takes
> a config file to allow column mapping.... Not sure how general purpose
> it is... Anyone want to mess with it?
Well, I thought Andy was working on one?? Using the gnumeric format? I
might
be able to lend a hand on this as I've had to delve into HSSF for a wacky
requirement at work this spring. As I don't know gnumeric in the slightest,
I'll be pretty useless on that aspect.
Geoff
OT: XHSSF ( was: [VOTE] Move cocoon-poi-block stuff to POI)
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
Andrew C. Oliver wrote:
> I plan to make HSSFSerializer a light wrapper around "XHSSF"
eXtremely Horrible SpreadSheet Format?
(tickles my Horrible Marketing Machine - see
http://www.codeconsult.ch/blogs/bertrand-archives/000046.html)
I like both the idea and the lame name though.
-Bertrand
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by David Kavanagh <da...@dotech.com>.
Has anyone written an HSSFGenerator? I wrote an HSSFTransformer... Takes
a config file to allow column mapping.... Not sure how general purpose
it is... Anyone want to mess with it?
David
Vadim Gritsenko wrote:
> Andrew C. Oliver wrote:
>
>> I plan to make HSSFSerializer a light wrapper around "XHSSF"
>>
>
> Way to go, +1!
>
>> (or some other lame name).
>>
>
> +10 for the lame name
>
> ;-)
> Vadim
>
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Vadim Gritsenko <va...@verizon.net>.
Andrew C. Oliver wrote:
>I plan to make HSSFSerializer a light wrapper around "XHSSF"
>
Way to go, +1!
>(or some other lame name).
>
+10 for the lame name
;-)
Vadim
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by "Andrew C. Oliver" <ac...@apache.org>.
I plan to make HSSFSerializer a light wrapper around "XHSSF" (or some other
lame name). This will migrate to a new POI-controlled XML format that
cleanly matches our conceptualization (over time as I need it or others
help). However I'd rather not wrap the vote into too many details. I'll
play as nice as I'm permitted to play :-) the details are just that.
-Andy
On 5/14/03 9:34 AM, "Carsten Ziegeler" <cz...@s-und-n.de> wrote:
> Vadim Gritsenko wrote:
>> Andrew C. Oliver wrote:
>>
>>> Cocoon folks please vote:
>>>
>>> [x] +1
>>> [ ] +0
>>> [ ] -0
>>> [ ] -1
>>>
>>>
>>
>> I presume you mean ms excel serialization classes. Block itself will
>> still be here and will include jar from POI with serialization classes
>> as well as samples.
>>
> Good point - can we please clarify what we really vote on here?
> Moving the complete block to POI or only the serialization classes?
>
> I'm +1 on moving serialization classes, but only +0 for moving the
> complete block unless we have implemented the "real blocks" (damn, I said
> that we will get confused by naming the current separation 'blocks')
> to simply drop in "remote" blocks (or we have a block repository).
>
> Carsten (dreaming more and more about the "real blocks")
--
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?
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by "Andrew C. Oliver" <ac...@apache.org>.
I plan to make HSSFSerializer a light wrapper around "XHSSF" (or some other
lame name). This will migrate to a new POI-controlled XML format that
cleanly matches our conceptualization (over time as I need it or others
help). However I'd rather not wrap the vote into too many details. I'll
play as nice as I'm permitted to play :-) the details are just that.
-Andy
On 5/14/03 9:34 AM, "Carsten Ziegeler" <cz...@s-und-n.de> wrote:
> Vadim Gritsenko wrote:
>> Andrew C. Oliver wrote:
>>
>>> Cocoon folks please vote:
>>>
>>> [x] +1
>>> [ ] +0
>>> [ ] -0
>>> [ ] -1
>>>
>>>
>>
>> I presume you mean ms excel serialization classes. Block itself will
>> still be here and will include jar from POI with serialization classes
>> as well as samples.
>>
> Good point - can we please clarify what we really vote on here?
> Moving the complete block to POI or only the serialization classes?
>
> I'm +1 on moving serialization classes, but only +0 for moving the
> complete block unless we have implemented the "real blocks" (damn, I said
> that we will get confused by naming the current separation 'blocks')
> to simply drop in "remote" blocks (or we have a block repository).
>
> Carsten (dreaming more and more about the "real blocks")
--
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?
RE: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Vadim Gritsenko wrote:
> Andrew C. Oliver wrote:
>
> >Cocoon folks please vote:
> >
> >[x] +1
> >[ ] +0
> >[ ] -0
> >[ ] -1
> >
> >
>
> I presume you mean ms excel serialization classes. Block itself will
> still be here and will include jar from POI with serialization classes
> as well as samples.
>
Good point - can we please clarify what we really vote on here?
Moving the complete block to POI or only the serialization classes?
I'm +1 on moving serialization classes, but only +0 for moving the
complete block unless we have implemented the "real blocks" (damn, I said
that we will get confused by naming the current separation 'blocks')
to simply drop in "remote" blocks (or we have a block repository).
Carsten (dreaming more and more about the "real blocks")
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Bertrand Delacretaz <bd...@codeconsult.ch>.
> Andrew C. Oliver wrote:
>
>> Cocoon folks please vote:
+1
> I presume you mean ms excel serialization classes. Block itself will
> still be here and will include jar from POI with serialization classes
> as well as samples.
>
> Vadim
+1 on this too
-Bertrand
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Vadim Gritsenko <va...@verizon.net>.
Andrew C. Oliver wrote:
>Cocoon folks please vote:
>
>[x] +1
>[ ] +0
>[ ] -0
>[ ] -1
>
>
I presume you mean ms excel serialization classes. Block itself will
still be here and will include jar from POI with serialization classes
as well as samples.
Vadim
Re: [VOTE] Move cocoon-poi-block stuff to POI
Posted by Avik Sengupta <av...@apache.org>.
+1
On Wed, 2003-05-14 at 06:41, Andrew C. Oliver wrote:
> Cocoon folks please vote:
>
> [ ] +1
> [ ] +0
> [ ] -0
> [ ] -1
>
> POI Folks please vote on accepting this:
>
> [ ] +1
> [ ] +0
> [ ] -0
> [ ] -1
>
> For explanations read below. I'm too tired to recite it all and be fancy.
>
> -Andy
>
> On 5/13/03 12:54 PM, "Stefano Mazzocchi" <st...@apache.org> wrote:
>
> > on 5/13/03 7:04 AM Andrew C. Oliver wrote:
> >
> >> 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)
> >
> > I'd be in favor of moving that code to POI. Nobody else uses it and we
> > don't know how to manage/fix it.
> >
> > I strongly believe code should reside where there is a community that
> > maintains it, not where it makes more sense architecturally.
> >
> > But sometimes I don't find other people resonating with this vision so
> > count this as only my personal opinion.
>
> --
> 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?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: poi-dev-help@jakarta.apache.org
>
[VOTE] Move cocoon-poi-block stuff to POI
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Cocoon folks please vote:
[ ] +1
[ ] +0
[ ] -0
[ ] -1
POI Folks please vote on accepting this:
[ ] +1
[ ] +0
[ ] -0
[ ] -1
For explanations read below. I'm too tired to recite it all and be fancy.
-Andy
On 5/13/03 12:54 PM, "Stefano Mazzocchi" <st...@apache.org> wrote:
> on 5/13/03 7:04 AM Andrew C. Oliver wrote:
>
>> 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)
>
> I'd be in favor of moving that code to POI. Nobody else uses it and we
> don't know how to manage/fix it.
>
> I strongly believe code should reside where there is a community that
> maintains it, not where it makes more sense architecturally.
>
> But sometimes I don't find other people resonating with this vision so
> count this as only my personal opinion.
--
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?
[VOTE] Move cocoon-poi-block stuff to POI
Posted by "Andrew C. Oliver" <ac...@apache.org>.
Cocoon folks please vote:
[ ] +1
[ ] +0
[ ] -0
[ ] -1
POI Folks please vote on accepting this:
[ ] +1
[ ] +0
[ ] -0
[ ] -1
For explanations read below. I'm too tired to recite it all and be fancy.
-Andy
On 5/13/03 12:54 PM, "Stefano Mazzocchi" <st...@apache.org> wrote:
> on 5/13/03 7:04 AM Andrew C. Oliver wrote:
>
>> 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)
>
> I'd be in favor of moving that code to POI. Nobody else uses it and we
> don't know how to manage/fix it.
>
> I strongly believe code should reside where there is a community that
> maintains it, not where it makes more sense architecturally.
>
> But sometimes I don't find other people resonating with this vision so
> count this as only my personal opinion.
--
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?
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by Stefano Mazzocchi <st...@apache.org>.
on 5/13/03 7:04 AM Andrew C. Oliver wrote:
> 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)
I'd be in favor of moving that code to POI. Nobody else uses it and we
don't know how to manage/fix it.
I strongly believe code should reside where there is a community that
maintains it, not where it makes more sense architecturally.
But sometimes I don't find other people resonating with this vision so
count this as only my personal opinion.
--
Stefano.
Re: [Proposal] All POI committers given access to POI block Re:
[GUMP] Build Failure - cocoon-block-poi
Posted by Stefano Mazzocchi <st...@apache.org>.
on 5/13/03 7:04 AM Andrew C. Oliver wrote:
> 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)
I'd be in favor of moving that code to POI. Nobody else uses it and we
don't know how to manage/fix it.
I strongly believe code should reside where there is a community that
maintains it, not where it makes more sense architecturally.
But sometimes I don't find other people resonating with this vision so
count this as only my personal opinion.
--
Stefano.