Re: Preparing Cocoon 2.2-final

2007-10-16 Thread Hanne Moa
Vadim Gritsenko wrote:
> Reinhard Poetz wrote:
>>
>> As I announced in the RC2 voting thread, I think that it is time for
>> the final release of Cocoon 2.2. What issues are open that have to be
>> resolved by then? Here is the list of items that I've found:
>>
>>  - provide a migration guide (???)
>>
>>  - deprecation (???)
>>We have to deprecate everything that we want to remove in Cocoon 2.3.
>>(If nobody beats me, I will start off a discussion about this soon.)
>>
>>Deprecation means that we have to add the information to
>>src/changes/changes.xml, write out deprecation logs, add information
>>to the migration guide and set the @deprecated annotation.
>>
>>  - springification (???)
>>Some sitemap components have already been springified. We should
>> revert
>>this in trunk and work on the springification in a seperate branch.
>>
>>This way 2.1 sitemaps are 100 % compatible with 2.2.
>>
>>  - provide a binary release of Cocoon 2.2 (Reinhard)
>>
>>  - prepare the press release (Gianguo)
>>
>>  - servlet-service documentation (???)
>>The servlet-service framework has become a central part of Cocoon
>> and is
>>also useable without Cocoon core.
>>
>>  - add a functional tutorial that shows the power of Cocoon (Lars)
>>
>>
>> Anything else? If there are volonteers for the 4 open tasks (see ???),
>> we should be able to release by the end of November.

How about a samples block, or marking what will and won't work in the
samples for 2.1.10 on 2.2?


HM


Re: Site - Incorrect link to 'home'

2007-10-16 Thread Reinhard Poetz

Vadim Gritsenko wrote:

Hi,

New site has little 'home' icon in top-left corner with a link, but 
regardless of link text, it always points to the same place - 
http://cocoon.apache.org/, instead of home of the current module/block/etc:


http://cocoon.apache.org/2.2/blocks/ - "Cocoon Blocks 2.2" - points to /
http://cocoon.apache.org/2.2/core-modules/ - "Cocoon Core Modules 2.2" - 
points to /


Any ideas how to fix this?


should be simple to fix in the velocity template (coocon-thien-maven-site). I 
will have a look at it asap.


--
Reinhard PötzManaging Director, {Indoqa} GmbH
  http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_


[continuum] BUILD FAILURE: Apache Cocoon [build root]

2007-10-16 Thread Continuum VMBuild Server

Online report : 
http://vmbuild.apache.org/continuum/buildResult.action?buildId=14116&projectId=51

Build statistics:
 State: Failed
 Previous State: Ok
 Started at: Tue 16 Oct 2007 21:13:27 -0700
 Finished at: Tue 16 Oct 2007 21:17:21 -0700
 Total time: 3m 53s
 Build Trigger: Schedule
 Build Number: 57
 Exit code: 1
 Building machine hostname: vmbuild.apache.org
 Operating system : Linux(unknown)
 Java Home version : 
 java version "1.4.2_15"

 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
 Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode)
   
 Builder version :

 Maven version: 2.0.7
 Java version: 1.4.2_15
 OS name: "linux" version: "2.6.20-16-server" arch: "i386"
   


SCM Changes:

Changed: vgritsenko @ Tue 16 Oct 2007 20:08:33 -0700
Comment: saner logging defaults: tone down spring messages a notch.
Files changed:
 
/cocoon/trunk/core/cocoon-core/src/main/resources/META-INF/cocoon/properties/core.properties
 ( 585337 )
 
/cocoon/trunk/core/cocoon-core/src/main/resources/META-INF/cocoon/properties/dev/core.properties
 ( 585337 )
 /cocoon/trunk/core/cocoon-webapp/src/main/webapp/WEB-INF/cocoon/log4j.xml ( 
585337 )
 
/cocoon/trunk/tools/archetypes/cocoon-22-archetype-webapp/src/main/resources/archetype-resources/src/main/webapp/WEB-INF/log4j.xml
 ( 585337 )
 
/cocoon/trunk/tools/cocoon-maven-plugin/src/main/resources/org/apache/cocoon/maven/rcl/WEB-INF/log4j.xml
 ( 585337 )

Changed: vgritsenko @ Tue 16 Oct 2007 20:10:57 -0700
Comment: use new abstractlogenabled - commons logging
Files changed:
 
/cocoon/trunk/blocks/cocoon-apples/cocoon-apples-sample/src/main/java/org/apache/cocoon/components/flow/apples/samples/BindingWoodyApple.java
 ( 585341 )
 
/cocoon/trunk/blocks/cocoon-apples/cocoon-apples-sample/src/main/java/org/apache/cocoon/components/flow/apples/samples/CalculationApple.java
 ( 585341 )
 
/cocoon/trunk/blocks/cocoon-apples/cocoon-apples-sample/src/main/java/org/apache/cocoon/components/flow/apples/samples/GuessGameApple.java
 ( 585341 )
 
/cocoon/trunk/blocks/cocoon-apples/cocoon-apples-sample/src/main/java/org/apache/cocoon/components/flow/apples/samples/HanoiApple.java
 ( 585341 )

Changed: vgritsenko @ Tue 16 Oct 2007 20:11:14 -0700
Comment: use new abstractlogenabled - commons logging
Files changed:
 
/cocoon/trunk/blocks/cocoon-axis/cocoon-axis-impl/src/main/java/org/apache/cocoon/components/axis/SoapServer.java
 ( 585342 )
 
/cocoon/trunk/blocks/cocoon-axis/cocoon-axis-impl/src/main/java/org/apache/cocoon/components/axis/SoapServerImpl.java
 ( 585342 )
 
/cocoon/trunk/blocks/cocoon-axis/cocoon-axis-impl/src/main/java/org/apache/cocoon/webservices/AbstractLogEnabledService.java
 ( 585342 )

Changed: vgritsenko @ Tue 16 Oct 2007 20:37:19 -0700
Comment: fix exception handling - there could be a situation with ignored 
exception
Files changed:
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/components/source/impl/CachingSource.java
 ( 585350 )

Changed: vgritsenko @ Tue 16 Oct 2007 20:52:17 -0700
Comment: iuse new abstractlogenabled - commons logging
Files changed:
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/components/crawler/SimpleCocoonCrawlerImpl.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/components/persistence/RequestDataStoreImpl.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/components/source/CocoonSourceResolver.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/components/source/helpers/DelaySourceRefresher.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/components/source/impl/BlockContextSourceFactory.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/i18n/XMLResourceBundle.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/i18n/XMLResourceBundleFactory.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/transformation/helpers/DefaultIncludeCacheManager.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/transformation/helpers/ModifiableSourceIncludeCacheStorageProxy.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/transformation/helpers/StoreIncludeCacheStorageProxy.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/xml/LoggingContentHandler.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/main/java/org/apache/cocoon/xml/LoggingEntityResolver.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/test/java/org/apache/cocoon/components/source/impl/XMLizableSource.java
 ( 585353 )
 
/cocoon/trunk/core/cocoon-core/src/test/java/org/apache/cocoon/components/source/impl/XMLizableSourceFa

Site - Incorrect link to 'home'

2007-10-16 Thread Vadim Gritsenko

Hi,

New site has little 'home' icon in top-left corner with a link, but regardless 
of link text, it always points to the same place - http://cocoon.apache.org/, 
instead of home of the current module/block/etc:


http://cocoon.apache.org/2.2/blocks/ - "Cocoon Blocks 2.2" - points to /
http://cocoon.apache.org/2.2/core-modules/ - "Cocoon Core Modules 2.2" - points 
to /

Any ideas how to fix this?

Vadim


ForrestBot build for cocoon-docs FAILED

2007-10-16 Thread Forrestbot
Automated build for cocoon-docs FAILED
Log attached.

--
Forrestbot run ended at 17 October 12:30 AM
Using Forrest 0.9-dev
Forrestbot administrator: ForrestBot
--

 [echo] 
  ... Forrest render START 2007-10-17 12:02:38
  ... Rendering docs in 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs


check-java-version:
 [echo] This is apache-forrest-0.9-dev
 [echo] Using Java 1.4 from /usr/j2se/jre

init-props:
[mkdir] Created dir: 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp

echo-settings:

check-skin:

init-proxy:

fetch-skins-descriptors:

fetch-skin:

unpack-skins:

init-skins:

fetch-plugins-descriptors:
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [echo] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/plugins.xml
  [get] Getting: http://forrest.apache.org/plugins/plugins.xml
  [get] To: 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-1.xml
  [get] local file date : Tue Apr 10 05:50:24 GMT+00:00 2007
  [get] .
  [get] last modified = Wed Apr 11 02:07:04 GMT+00:00 2007
 [echo] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/whiteboard-plugins.xml
  [get] Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
  [get] To: 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-2.xml
  [get] local file date : Sat Sep 01 21:45:45 GMT+00:00 2007
  [get] Not modified - so not downloaded
 [echo] Plugin list loaded from 
http://forrest.apache.org/plugins/plugins.xml.
 [echo] Plugin list loaded from 
http://forrest.apache.org/plugins/whiteboard-plugins.xml.

init-plugins:
[mkdir] Created dir: 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/webapp/conf
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [echo] 
  --
  Installing plugin: org.apache.forrest.plugin.output.pdf
  --
   

check-plugin:
 [echo] org.apache.forrest.plugin.output.pdf is available in the build dir. 
Trying to update it...

init-props:

echo-settings:

init-proxy:

fetch-plugins-descriptors:

fetch-plugin:
 [echo] Trying to find the description of 
org.apache.forrest.plugin.output.pdf in the different descriptor files
 [echo] Using the descriptor file 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-1.xml...
 [xslt] Processing 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-1.xml to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/pluginlist2fetchbuild.xml
 [xslt] Loading stylesheet 
/export/opt/forrest-trunk/main/var/pluginlist2fetch.xsl

fetch-local-unversioned-plugin:

get-local:
 [echo] Trying to locally get org.apache.forrest.plugin.output.pdf
 [echo] Looking in local /export/opt/forrest-trunk/plugins
 [echo] Found !

init-build-compiler:

echo-init:

init:

compile:

jar:

local-deploy:
 [echo] Locally deploying org.apache.forrest.plugin.output.pdf

build:
 [echo] Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to 
configure

fetch-remote-unversioned-plugin-version-forrest:

fetch-remote-unversioned-plugin-unversion-forrest:

has-been-downloaded:

downloaded-message:

uptodate-message:

not-found-message:
 [echo] Fetch-plugin Ok, installing !

unpack-plugin:

install-plugin:

configure-plugin:

configure-output-plugin:
 [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf
 [xslt] Processing 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/output.xmap to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/output.xmap.new
 [xslt] Loading stylesheet 
/export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl
 [move] Moving 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp

configure-plugin-locationmap:
 [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf
 [xslt] Processing 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/locationmap.xml 
to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/locationmap.xml.new
 [xslt] Loading stylesheet 
/export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl
 [move] Moving 1 file to 
/export/home/config/forrestbot-t

Re: Preparing Cocoon 2.2-final

2007-10-16 Thread Grzegorz Kossakowski
Vadim Gritsenko pisze:
> Reinhard Poetz wrote:
>>
>> As I announced in the RC2 voting thread, I think that it is time for
>> the final release of Cocoon 2.2. What issues are open that have to be
>> resolved by then? Here is the list of items that I've found:
>>
>>  - provide a migration guide (???)
>>
>>  - deprecation (???)
>>We have to deprecate everything that we want to remove in Cocoon 2.3.
>>(If nobody beats me, I will start off a discussion about this soon.)
>>
>>Deprecation means that we have to add the information to
>>src/changes/changes.xml, write out deprecation logs, add information
>>to the migration guide and set the @deprecated annotation.
>>
>>  - springification (???)
>>Some sitemap components have already been springified. We should
>> revert
>>this in trunk and work on the springification in a seperate branch.
>>
>>This way 2.1 sitemaps are 100 % compatible with 2.2.
>>
>>  - provide a binary release of Cocoon 2.2 (Reinhard)
>>
>>  - prepare the press release (Gianguo)
>>
>>  - servlet-service documentation (???)
>>The servlet-service framework has become a central part of Cocoon
>> and is
>>also useable without Cocoon core.
>>
>>  - add a functional tutorial that shows the power of Cocoon (Lars)
>>
>>
>> Anything else? If there are volonteers for the 4 open tasks (see ???),
>> we should be able to release by the end of November.
> 
> List looks good to me. Personally I'd also like to fix COCOON-1985
> before final release.
> 
> Grzegorz - you were saying you started doing changes related to this bug
> (using call stack instead of environment stack) - are there any updates
> on this? I don't want to step on your toes :)

Nope, no updates, unfortunately. I'm busy with catching up with classes I 
missed during GT at the
moment. Everything happens so quickly at my university and I missed a lot of 
interesting stuff of
topology, analysis and so on. :-)
I fear that until next Monday I will be hardly following discussions not even 
mentioning any work on
Cocoon.

To sum up, I don't work on this now and I must limit my activity to only 
helping others so you can
safely work on COCOON-1985.

-- 
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
http://reflectingonthevicissitudes.wordpress.com/


Re: AbstractLogEnabled...

2007-10-16 Thread Reinhard Poetz

Vadim Gritsenko wrote:

Reinhard Poetz wrote:
For me the most important aspect in this matter is that users 
shouldn't be forced to recompile their stuff if they don't want to.


I don't think this is a realistic expectation for the major (2.X is 
major in our numbering scheme) release. I'd totally agree with you on 
minor upgrade, such as 2.1.9 to 2.1.10.



Switching to Cocoon 2.3 (2.5 or 3.0 - whatever we will name it) will 
change the contracts for components fundamentally. This means that all 
exisiting components need to be rewritten anyway


Why?


will Avalon interfaces, e.g. Configureable, still be supported?

--
Reinhard PötzManaging Director, {Indoqa} GmbH
  http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_


Re: AbstractLogEnabled...

2007-10-16 Thread Carsten Ziegeler
Vadim Gritsenko wrote:
> Carsten Ziegeler wrote:
> 
> Ok - no enableLogging. But what about previous questions? To avoid
> dependency, switch should be made, isn't it?
> 
Yes. It's not required for 2.2 but we should definitly have it replaced
for 2.3; the sooner the better, so if you want to go ahead, +1. :)


> 
>> Now, today, I think even this class can be removed as it creates an
>> unnecessary dependency to the module containing it. If you want to log,
>> just instantiate the commons logger in your own code and use it.
> 
> But this adds a dependency on commons logging ;-)
:)

> 
> 
>> If you
>> want to make it configurable, provide a setLogger() method like this
>> abstract class does.
> 
> IMHO it is cleaner to use a base class. No need to replicate logging
> stuff everywhere - it is easier to extend from common base class (where
> it is possible / makes sense)
Yes, "where it makes sense" is the key here :) Getting the logger for
commons logging is one line of code (and it's a short line), so you
don't gain much if you have a base class with this one line. I think we
can use the base class where we have a dependency to the module with the
base class anyway. In other cases we should avoid it.

Carsten
-- 
Carsten Ziegeler
[EMAIL PROTECTED]


Re: AbstractLogEnabled...

2007-10-16 Thread Vadim Gritsenko

Reinhard Poetz wrote:
For me the most 
important aspect in this matter is that users shouldn't be forced to 
recompile their stuff if they don't want to.


I don't think this is a realistic expectation for the major (2.X is major in our 
numbering scheme) release. I'd totally agree with you on minor upgrade, such as 
2.1.9 to 2.1.10.



Switching to Cocoon 2.3 (2.5 or 3.0 - whatever we will name it) will 
change the contracts for components fundamentally. This means that all 
exisiting components need to be rewritten anyway


Why?

Vadim


Re: AbstractLogEnabled...

2007-10-16 Thread Vadim Gritsenko

Carsten Ziegeler wrote:

Vadim Gritsenko wrote:

Hi,

Ok I'm confused about AbstractLogEnabled business. Is it correct that
instead of org.apache.avalon.framework.logger.AbstractLogEnabled we
should be using org.apache.cocoon.util.AbstractLogEnabled [1]?

If yes, why there are only 2 usages of the latter and around 100 usages
of the former? :)

Should I go ahead and do a replacement? Or may be we should discuss it
first. For example, should there be an implementation of
enableLogging(org.apache.avalon.framework.logger.Logger logger) method
to provide backward compatibility.


No, I don't think so - one of the main ideas of this base class is to
avoid dependencies to Avalon.


Ok - no enableLogging. But what about previous questions? To avoid dependency, 
switch should be made, isn't it?




Now, today, I think even this class can be removed as it creates an
unnecessary dependency to the module containing it. If you want to log,
just instantiate the commons logger in your own code and use it.


But this adds a dependency on commons logging ;-)



If you
want to make it configurable, provide a setLogger() method like this
abstract class does.


IMHO it is cleaner to use a base class. No need to replicate logging stuff 
everywhere - it is easier to extend from common base class (where it is possible 
/ makes sense)


Vadim


Re: [DAISY] Updated: Cocoon 2.2 Migration Guide

2007-10-16 Thread Vadim Gritsenko

Reinhard Poetz wrote:

[EMAIL PROTECTED] wrote:

A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1419.html

Document ID: 1419
Branch: main
Language: default
Name: Cocoon 2.2 Migration Guide (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 10/16/07 3:24:54 PM
Updated by: Vadim Gritsenko


Thanks for taking care for this. One thing: The document is currently 
added to the "cdocs" collection.


Isn't this document in cdocs collection as well?
http://cocoon.zones.apache.org/daisy/cdocs/g2/g2/1327.html

They are side by side on the navigation bar.


Could you please add it to the 
"cdocs-site-22" collection instead? (This happened because you the 
"cdocs" site in Daisy was active when you created the document.)


I'm not sure how to do it. There is nothing in the menu that would sound 
relevant.

Vadim


Re: AbstractLogEnabled...

2007-10-16 Thread Carsten Ziegeler
Vadim Gritsenko wrote:
> Hi,
> 
> Ok I'm confused about AbstractLogEnabled business. Is it correct that
> instead of org.apache.avalon.framework.logger.AbstractLogEnabled we
> should be using org.apache.cocoon.util.AbstractLogEnabled [1]?
> 
> If yes, why there are only 2 usages of the latter and around 100 usages
> of the former? :)
> 
> Should I go ahead and do a replacement? Or may be we should discuss it
> first. For example, should there be an implementation of
> enableLogging(org.apache.avalon.framework.logger.Logger logger) method
> to provide backward compatibility.
> 
No, I don't think so - one of the main ideas of this base class is to
avoid dependencies to Avalon.

Now, today, I think even this class can be removed as it creates an
unnecessary dependency to the module containing it. If you want to log,
just instantiate the commons logger in your own code and use it. If you
want to make it configurable, provide a setLogger() method like this
abstract class does.

Carsten

-- 
Carsten Ziegeler
[EMAIL PROTECTED]


Re: [DAISY] Updated: Cocoon 2.2 Migration Guide

2007-10-16 Thread Reinhard Poetz

[EMAIL PROTECTED] wrote:

A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1419.html

Document ID: 1419
Branch: main
Language: default
Name: Cocoon 2.2 Migration Guide (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 10/16/07 3:24:54 PM
Updated by: Vadim Gritsenko


Thanks for taking care for this. One thing: The document is currently added to 
the "cdocs" collection. Could you please add it to the "cdocs-site-22" 
collection instead? (This happened because you the "cdocs" site in Daisy was 
active when you created the document.)


Thanks!

--
Reinhard PötzManaging Director, {Indoqa} GmbH
  http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_


Re: AbstractLogEnabled...

2007-10-16 Thread Reinhard Poetz

Vadim Gritsenko wrote:

Hi,

Ok I'm confused about AbstractLogEnabled business. Is it correct that 
instead of org.apache.avalon.framework.logger.AbstractLogEnabled we 
should be using org.apache.cocoon.util.AbstractLogEnabled [1]?


If yes, why there are only 2 usages of the latter and around 100 usages 
of the former? :)


Should I go ahead and do a replacement? Or may be we should discuss it 
first. For example, should there be an implementation of 
enableLogging(org.apache.avalon.framework.logger.Logger logger) method 
to provide backward compatibility.


This logging thing always confuses me too (how does it come that such a simple 
thing like logging can be so painful *sig*). For me the most important aspect in 
this matter is that users shouldn't be forced to recompile their stuff if they 
don't want to.


Switching to Cocoon 2.3 (2.5 or 3.0 - whatever we will name it) will change the 
contracts for components fundamentally. This means that all exisiting components 
need to be rewritten anyway and changing logging should carry no weight.


--
Reinhard PötzManaging Director, {Indoqa} GmbH
  http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_


AbstractLogEnabled...

2007-10-16 Thread Vadim Gritsenko

Hi,

Ok I'm confused about AbstractLogEnabled business. Is it correct that instead of 
org.apache.avalon.framework.logger.AbstractLogEnabled we should be using 
org.apache.cocoon.util.AbstractLogEnabled [1]?


If yes, why there are only 2 usages of the latter and around 100 usages of the 
former? :)


Should I go ahead and do a replacement? Or may be we should discuss it first. 
For example, should there be an implementation of 
enableLogging(org.apache.avalon.framework.logger.Logger logger) method to 
provide backward compatibility.


Vadim

[1] http://cocoon.zones.apache.org/daisy/cdocs/g2/g2/1419.html


Re: Preparing Cocoon 2.2-final

2007-10-16 Thread Vadim Gritsenko

Reinhard Poetz wrote:


As I announced in the RC2 voting thread, I think that it is time for the 
final release of Cocoon 2.2. What issues are open that have to be 
resolved by then? Here is the list of items that I've found:


 - provide a migration guide (???)

 - deprecation (???)
   We have to deprecate everything that we want to remove in Cocoon 2.3.
   (If nobody beats me, I will start off a discussion about this soon.)

   Deprecation means that we have to add the information to
   src/changes/changes.xml, write out deprecation logs, add information
   to the migration guide and set the @deprecated annotation.

 - springification (???)
   Some sitemap components have already been springified. We should revert
   this in trunk and work on the springification in a seperate branch.

   This way 2.1 sitemaps are 100 % compatible with 2.2.

 - provide a binary release of Cocoon 2.2 (Reinhard)

 - prepare the press release (Gianguo)

 - servlet-service documentation (???)
   The servlet-service framework has become a central part of Cocoon and is
   also useable without Cocoon core.

 - add a functional tutorial that shows the power of Cocoon (Lars)


Anything else? If there are volonteers for the 4 open tasks (see ???), 
we should be able to release by the end of November.


List looks good to me. Personally I'd also like to fix COCOON-1985 before final 
release.


Grzegorz - you were saying you started doing changes related to this bug (using 
call stack instead of environment stack) - are there any updates on this? I 
don't want to step on your toes :)


Vadim


Re: [jira] Created: (COCOON-2140) Problems using lenya 1.2 with JBOSS application server. doesnt generate pages.

2007-10-16 Thread Joerg Heinicke

Hey Lenya developers,

would be nice if you could change the template that is used for 
displaying an error so that you get these reports and not Cocoon :-)


Regards
Joerg

On 16.10.2007 9:04 Uhr, Anirudhdha Jani (JIRA) wrote:


Problems using lenya 1.2  with JBOSS application server. doesnt generate pages.
---

 Key: COCOON-2140
 URL: https://issues.apache.org/jira/browse/COCOON-2140
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Reporter: Anirudhdha Jani


An Error Occurred

C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)

org.apache.lenya.cms.task.ExecutionException: C:\Program 
Files\jboss-4.0.5.GA\server\default\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\config\tasks\targets.xml:139:
 org.apache.lenya.cms.authoring.CreatorException: 
javax.xml.transform.TransformerException: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)

cause: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)

full exception chain stacktrace[hide]

org.apache.lenya.cms.task.ExecutionException: C:\Program 
Files\jboss-4.0.5.GA\server\default\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\config\tasks\targets.xml:139:
 org.apache.lenya.cms.authoring.CreatorException: 
javax.xml.transform.TransformerException: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)
at org.apache.lenya.cms.task.AntTask.executeAntTarget(AntTask.java:128)
at org.apache.lenya.cms.task.AntTask.execute(AntTask.java:228)
at 
org.apache.lenya.cms.task.DefaultTaskWrapper.execute(DefaultTaskWrapper.java:245)
at org.apache.lenya.cms.cocoon.acting.TaskAction.act(TaskAction.java:63)
at 
org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:124)

...

Caused by: C:\Program 
Files\jboss-4.0.5.GA\server\default\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\config\tasks\targets.xml:139:
 org.apache.lenya.cms.authoring.CreatorException: 
javax.xml.transform.TransformerException: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)
at 
org.apache.lenya.cms.ant.DocumentCreatorTask.execute(DocumentCreatorTask.java:60)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at org.apache.lenya.cms.task.AntTask.executeAntTarget(AntTask.java:125)
... 61 more
Caused by: org.apache.lenya.cms.authoring.CreatorException: 
javax.xml.transform.TransformerException: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)
at 
org.apache.lenya.cms.authoring.DocumentCreator.create(DocumentCreator.java:145)
at 
org.apache.lenya.cms.ant.DocumentCreatorTask.execute(DocumentCreatorTask.java:48)
... 68 more
Caused by: javax.xml.transform.TransformerException: 
java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)
at 
org.apache.xalan.transformer.TransformerIdentityImpl.createResultContentHandler(TransformerIdentityImpl.java:296)
at 
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:329)
at 
org.apache.lenya.xml.DocumentHelper.writeDocument(DocumentHelper.java:200)
at 
org.apache.lenya.cms.authoring.DefaultCreator.create(DefaultCreator.java:182)
at 
org.apache.lenya.cms.authoring.DocumentCreator.create(DocumentCreator.java:133)
... 69 more
Caused by: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227l

Re: [vote] Releasing from trunk: Cocoon 2.2-RC2 & others

2007-10-16 Thread Joerg Heinicke

On 15.10.2007 3:38 Uhr, Reinhard Poetz wrote:


I've prepared another series of releases from trunk, see the list of all 45
artifacts below. This time most of the modules are proposed to be 
released as "RC2" (release candidate 2) or "RC1".


+1

Joerg


[jira] Closed: (COCOON-2140) Problems using lenya 1.2 with JBOSS application server. doesnt generate pages.

2007-10-16 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/COCOON-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jörg Heinicke closed COCOON-2140.
-

Resolution: Invalid

If I'm not mistaken this should be a Lenya issue. Lenya still uses Bugzilla as 
its bug tracking system as I read at 
http://lenya.apache.org/community/index.html. Please report the issue there 
since I can't move the bug over there.

> Problems using lenya 1.2  with JBOSS application server. doesnt generate 
> pages.
> ---
>
> Key: COCOON-2140
> URL: https://issues.apache.org/jira/browse/COCOON-2140
> Project: Cocoon
>  Issue Type: Bug
>  Components: * Cocoon Core
>Reporter: Anirudhdha Jani
>
> An Error Occurred
> C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
>  (The system cannot find the path specified)
> org.apache.lenya.cms.task.ExecutionException: C:\Program 
> Files\jboss-4.0.5.GA\server\default\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\config\tasks\targets.xml:139:
>  org.apache.lenya.cms.authoring.CreatorException: 
> javax.xml.transform.TransformerException: java.io.FileNotFoundException: 
> C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
>  (The system cannot find the path specified)
> cause: java.io.FileNotFoundException: 
> C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
>  (The system cannot find the path specified)
> full exception chain stacktrace[hide]
> org.apache.lenya.cms.task.ExecutionException: C:\Program 
> Files\jboss-4.0.5.GA\server\default\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\config\tasks\targets.xml:139:
>  org.apache.lenya.cms.authoring.CreatorException: 
> javax.xml.transform.TransformerException: java.io.FileNotFoundException: 
> C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
>  (The system cannot find the path specified)
>   at org.apache.lenya.cms.task.AntTask.executeAntTarget(AntTask.java:128)
>   at org.apache.lenya.cms.task.AntTask.execute(AntTask.java:228)
>   at 
> org.apache.lenya.cms.task.DefaultTaskWrapper.execute(DefaultTaskWrapper.java:245)
>   at org.apache.lenya.cms.cocoon.acting.TaskAction.act(TaskAction.java:63)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:124)
>   at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
>   at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
>   at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
>   at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142)
>   at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:92)
>   at 
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:234)
>   at 
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:176)
>   at 
> org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:252)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:117)
>   at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
>   at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
>   at 
> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142)
>   at 
> org.ap

Re: [vote] Releasing from trunk: Cocoon 2.2-RC2 & others

2007-10-16 Thread Vadim Gritsenko

Reinhard Poetz wrote:


I've prepared another series of releases from trunk, see the list of all 45
artifacts below.

...

 - cocoon-configuration-api-1.0.1.jar
 - cocoon-spring-configurator-1.0.1.jar
 - cocoon-servlet-service-impl-1.0.0-RC1.jar
 - cocoon-servlet-service-components-1.0.0-RC1.jar
 - cocoon-xml-api-1.0.0-RC2.jar
 - cocoon-xml-impl-1.0.0-RC2.jar
 - cocoon-xml-resolver-1.0.0-RC2.jar
 - cocoon-xml-util-1.0.0-RC2.jar
 - cocoon-thread-api-1.0.0-RC2.jar
 - cocoon-thread-impl-1.0.0-RC2.jar
 - cocoon-expression-language-api-1.0.0-RC2.jar
 - cocoon-expression-language-impl-1.0.0-RC2.jar
 - cocoon-util-1.0.0-RC2.jar
 - cocoon-store-impl-1.0.0-RC2.jar
 - cocoon-pipeline-api-1.0.0-RC2.jar
 - cocoon-pipeline-impl-1.0.0-RC2.jar
 - cocoon-pipeline-impl-1.0.0-RC2-tests.jar
 - cocoon-pipeline-components-1.0.0-RC2.jar
 - cocoon-sitemap-api-1.0.0-RC2.jar
 - cocoon-sitemap-impl-1.0.0-RC2.jar
 - cocoon-sitemap-impl-1.0.0-RC2-tests.jar
 - cocoon-sitemap-components-1.0.0-RC2.jar
 - cocoon-core-2.2.0-RC2.jar
 - cocoon-core-2.2.0-RC2-tests.jar
 - cocoon-template-impl-1.0.0-RC2.jar
 - cocoon-flowscript-impl-1.0.0-RC2.jar
 - cocoon-auth-api-1.0.0-RC2.jar
 - cocoon-auth-impl-1.0.0-RC2.jar
 - cocoon-batik-impl-1.0.0-RC2.jar
 - cocoon-captcha-impl-1.0.0-RC2.jar
 - cocoon-fop-impl-1.0.0-RC2.jar
 - cocoon-html-impl-1.0.0-RC2.jar
 - cocoon-linkrewriter-impl-1.0.0-RC2.jar
 - cocoon-mail-impl-1.0.0-RC2.jar
 - cocoon-databases-hsqldb-client-1.0.0-RC2.jar
 - cocoon-databases-hsqldb-server-1.0.0-RC2.jar
 - cocoon-databases-mocks-1.0.0-RC2.jar
 - cocoon-databases-impl-1.0.0-RC2.jar
 - cocoon-ajax-impl-1.0.0-RC1.jar
 - cocoon-apples-impl-1.0.0-RC2.jar
 - cocoon-forms-impl-1.0.0-RC1.jar
 - cocoon-22-archetype-block-1.0.0-RC2.jar
 - cocoon-22-archetype-block-plain-1.0.0-RC2.jar
 - cocoon-22-archetype-webapp-1.0.0-RC2.jar
 - cocoon-maven-javadocs-script-report-1.0.0-M1.jar[1]


+1

Vadim


[jira] Created: (COCOON-2140) Problems using lenya 1.2 with JBOSS application server. doesnt generate pages.

2007-10-16 Thread Anirudhdha Jani (JIRA)
Problems using lenya 1.2  with JBOSS application server. doesnt generate pages.
---

 Key: COCOON-2140
 URL: https://issues.apache.org/jira/browse/COCOON-2140
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Reporter: Anirudhdha Jani


An Error Occurred

C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)

org.apache.lenya.cms.task.ExecutionException: C:\Program 
Files\jboss-4.0.5.GA\server\default\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\config\tasks\targets.xml:139:
 org.apache.lenya.cms.authoring.CreatorException: 
javax.xml.transform.TransformerException: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)

cause: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)

full exception chain stacktrace[hide]

org.apache.lenya.cms.task.ExecutionException: C:\Program 
Files\jboss-4.0.5.GA\server\default\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\config\tasks\targets.xml:139:
 org.apache.lenya.cms.authoring.CreatorException: 
javax.xml.transform.TransformerException: java.io.FileNotFoundException: 
C:\Program%20Files\jboss-4.0.5.GA\server\default\.\tmp\deploy\tmp10227lenya-exp.war\lenya\pubs\default\content\authoring\foo\index_en.xml
 (The system cannot find the path specified)
at org.apache.lenya.cms.task.AntTask.executeAntTarget(AntTask.java:128)
at org.apache.lenya.cms.task.AntTask.execute(AntTask.java:228)
at 
org.apache.lenya.cms.task.DefaultTaskWrapper.execute(DefaultTaskWrapper.java:245)
at org.apache.lenya.cms.cocoon.acting.TaskAction.act(TaskAction.java:63)
at 
org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:124)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:92)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:234)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:176)
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:252)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:117)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:92)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:234)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:176)
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor

ForrestBot build for cocoon-docs FAILED

2007-10-16 Thread Forrestbot
Automated build for cocoon-docs FAILED
Log attached.

--
Forrestbot run ended at 16 October 12:34 PM
Using Forrest 0.9-dev
Forrestbot administrator: ForrestBot
--

 [echo] 
  ... Forrest render START 2007-10-16 12:02:30
  ... Rendering docs in 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs


check-java-version:
 [echo] This is apache-forrest-0.9-dev
 [echo] Using Java 1.4 from /usr/j2se/jre

init-props:
[mkdir] Created dir: 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp

echo-settings:

check-skin:

init-proxy:

fetch-skins-descriptors:

fetch-skin:

unpack-skins:

init-skins:

fetch-plugins-descriptors:
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [echo] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/plugins.xml
  [get] Getting: http://forrest.apache.org/plugins/plugins.xml
  [get] To: 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-1.xml
  [get] local file date : Tue Apr 10 05:50:24 GMT+00:00 2007
  [get] .
  [get] last modified = Wed Apr 11 02:07:04 GMT+00:00 2007
 [echo] Fetching plugins descriptor: 
http://forrest.apache.org/plugins/whiteboard-plugins.xml
  [get] Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
  [get] To: 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-2.xml
  [get] local file date : Sat Sep 01 21:45:45 GMT+00:00 2007
  [get] Not modified - so not downloaded
 [echo] Plugin list loaded from 
http://forrest.apache.org/plugins/plugins.xml.
 [echo] Plugin list loaded from 
http://forrest.apache.org/plugins/whiteboard-plugins.xml.

init-plugins:
[mkdir] Created dir: 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/webapp/conf
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [copy] Copying 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp
 [echo] 
  --
  Installing plugin: org.apache.forrest.plugin.output.pdf
  --
   

check-plugin:
 [echo] org.apache.forrest.plugin.output.pdf is available in the build dir. 
Trying to update it...

init-props:

echo-settings:

init-proxy:

fetch-plugins-descriptors:

fetch-plugin:
 [echo] Trying to find the description of 
org.apache.forrest.plugin.output.pdf in the different descriptor files
 [echo] Using the descriptor file 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-1.xml...
 [xslt] Processing 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/plugins-1.xml to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/pluginlist2fetchbuild.xml
 [xslt] Loading stylesheet 
/export/opt/forrest-trunk/main/var/pluginlist2fetch.xsl

fetch-local-unversioned-plugin:

get-local:
 [echo] Trying to locally get org.apache.forrest.plugin.output.pdf
 [echo] Looking in local /export/opt/forrest-trunk/plugins
 [echo] Found !

init-build-compiler:

echo-init:

init:

compile:

jar:

local-deploy:
 [echo] Locally deploying org.apache.forrest.plugin.output.pdf

build:
 [echo] Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to 
configure

fetch-remote-unversioned-plugin-version-forrest:

fetch-remote-unversioned-plugin-unversion-forrest:

has-been-downloaded:

downloaded-message:

uptodate-message:

not-found-message:
 [echo] Fetch-plugin Ok, installing !

unpack-plugin:

install-plugin:

configure-plugin:

configure-output-plugin:
 [echo] Mounting output plugin: org.apache.forrest.plugin.output.pdf
 [xslt] Processing 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/output.xmap to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/output.xmap.new
 [xslt] Loading stylesheet 
/export/opt/forrest-trunk/main/var/pluginMountSnippet.xsl
 [move] Moving 1 file to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp

configure-plugin-locationmap:
 [echo] Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf
 [xslt] Processing 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/locationmap.xml 
to 
/export/home/config/forrestbot-trunk/conf/work/cocoon-docs/tmp/locationmap.xml.new
 [xslt] Loading stylesheet 
/export/opt/forrest-trunk/main/var/pluginLmMountSnippet.xsl
 [move] Moving 1 file to 
/export/home/config/forrestbot-t

Re: Write access to the cocoon docs

2007-10-16 Thread Reinhard Poetz

Hanne Moa wrote:

I have the user "hm" at http://cocoon.zones.apache.org/daisy/ and would
like to do more than commenting. As in: fixing typos and other errors
and adding howtos and FAQs. On the GT it was said the thing to do was to
write here and ask for a role-change and by this mail I am doing so. 


I added you to the doc-editor group.


Oh,
and is the docs-list for anything else than autogenerated messages?


no, please keep all discussions on [EMAIL PROTECTED]

--
Reinhard PötzManaging Director, {Indoqa} GmbH
  http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair[EMAIL PROTECTED]
_


Write access to the cocoon docs

2007-10-16 Thread Hanne Moa
I have the user "hm" at http://cocoon.zones.apache.org/daisy/ and would
like to do more than commenting. As in: fixing typos and other errors
and adding howtos and FAQs. On the GT it was said the thing to do was to
write here and ask for a role-change and by this mail I am doing so. Oh,
and is the docs-list for anything else than autogenerated messages?


HM