DO NOT REPLY [Bug 34283] - Tutorial: Write a Custom Generator

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34283] - Tutorial: Write a Custom Generator

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Removing @author tags

Le 1 mai 05, à 22:46, Sylvain Wallez a écrit : ...So, I think it's really time to do some cleanup and remove these tags everywhere... Fine with me IIRC Bertrand ran a script to extract the current tags to build a credits file. Bertrand, any information on this? I did save the @author info in misc

[OT] Re: [RT] Cocoonlet

Actually, the idea of OSGi has been running in my head for a long time. I discovered OSGi when working on the embedded Cocoon, as we had to make an OSGi bundle with it so that it can be added to an OSGi-powered system in a car. OSGi is widely used in embedded systems, especially automotive and

DO NOT REPLY [Bug 34283] - Tutorial: Write a Custom Generator

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Removing @author tags

> So, I think it's really time to do some cleanup and remove these tags > everywhere. Not a big itch ...but sure > IIRC Bertrand ran a script to extract the current tags to build a > credits file. Bertrand, any information on this? Credits? Wondering how that would look like?! Do we need that at

Re: Hackathon at ApacheCon EU 2005? (was Re: [CANCELLED] Hackthon London 30 April/1st May 2005)

>> Well, I trying to work out something with Ben and >> the ApacheCon folks. AFAIK the official ApacheCon >> Hackathon starts on Monday ...but a few of us Cocoon >> folks would like to start and meet up on Sunday >> already. > > > I have just heard that we cannot use the conference > venue on Sun

DO NOT REPLY [Bug 34283] - Tutorial: Write a Custom Generator

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: [RT] Cocoonlet

On Dom, 1 de Mayo de 2005, 15:27, Sylvain Wallez dijo: > Daniel Fagerstrom wrote: > >> Sylvain Wallez wrote: > > > > >>> By using the Eclipse kernel, Cocoon could be the first RSP, "Rich >>> Server Platform". >>> >>> WDYT? >>> >>> Sylvain >>> >>> [1] http://www.eclipsefaq.org/chris/faq/faq-list.ht

Removing @author tags

Hi all, We decided a long time ago to remove @author tags, but never actually did it. In the meantime, most if not all new classes added since we made that decision have no author tag. This leads to a somewhat inconsistent state where only "old" authors are mentioned. So, I think it's really ti

Re: [RT] Cocoonlet

Daniel Fagerstrom wrote: Sylvain Wallez wrote: By using the Eclipse kernel, Cocoon could be the first RSP, "Rich Server Platform". WDYT? Sylvain [1] http://www.eclipsefaq.org/chris/faq/faq-list.html Cool! But not that you took my forthcomming RT ;) Ooops, sorry :-) I have also been thinking i

DO NOT REPLY [Bug 34696] - [PATCH] [docs] Updated Dev-Guide -> Avalon page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34696] New: - [PATCH] [docs] Updated Dev-Guide -> Avalon page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: svn commit: r165523 - /cocoon/trunk/src/java/org/apache/cocoon/reading/ImageReader.java

On Dom, 1 de Mayo de 2005, 11:57, Carsten Ziegeler dijo: > [EMAIL PROTECTED] wrote: >> Author: antonio >> Date: Sun May 1 09:42:58 2005 >> New Revision: 165523 >> >> URL: http://svn.apache.org/viewcvs?rev=165523&view=rev >> Log: >> Use SystemUtils to detect java 1.4 or higher >> > 2.2 requires 1.4

Re: svn commit: r165523 - /cocoon/trunk/src/java/org/apache/cocoon/reading/ImageReader.java

[EMAIL PROTECTED] wrote: > Author: antonio > Date: Sun May 1 09:42:58 2005 > New Revision: 165523 > > URL: http://svn.apache.org/viewcvs?rev=165523&view=rev > Log: > Use SystemUtils to detect java 1.4 or higher > 2.2 requires 1.4 or higher - so imho we don't need there test here. Carsten

Re: [VOTE] Time format for access time.

On Dom, 1 de Mayo de 2005, 10:31, Stefano Mazzocchi dijo: > Antonio Gallardo wrote: >> Hi: >> >> This is only related to the time format in the access output. Currently >> we >> use: >> >> Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds. >> Processed by Apache Cocoon 2.1.8-dev in 3 millisecon

Re: [VOTE] Time format for access time.

Antonio Gallardo wrote: Hi: This is only related to the time format in the access output. Currently we use: Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds. Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds. New format (an ISO8601-like): Processed by Apache Cocoon 2.1.8-dev in 0:00:03.61

Re: [VOTE] Time format for access time.

Il giorno 01/mag/05, alle 14:38, Antonio Gallardo ha scritto: Hi: This is only related to the time format in the access output. Currently we use: Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds. Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds. New format (an ISO8601-like): Processed

Re: [RT] Cocoonlet

Sylvain Wallez wrote: Sylvain Wallez wrote: Daniel Fagerstrom wrote: Our current (controversial ;) ) plan is to consider the sitemap and the component aspect of the original block proposal as separate concerns and (at least initially) solve them separately. Damn, I skipped this whole thread becau

Re: [VOTE] Time format for access time.

Antonio Gallardo wrote: Hi: This is only related to the time format in the access output. Currently we use: Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds. Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds. New format (an ISO8601-like): Processed by Apache Cocoon 2.1.8-dev in 0:00:03.61

Re: [RT] Cocoonlet

Sylvain Wallez wrote: Daniel Fagerstrom wrote: Our current (controversial ;) ) plan is to consider the sitemap and the component aspect of the original block proposal as separate concerns and (at least initially) solve them separately. Damn, I skipped this whole thread because I was overly swamp

[VOTE] Time format for access time.

Hi: This is only related to the time format in the access output. Currently we use: Processed by Apache Cocoon 2.1.8-dev in 3.612 seconds. Processed by Apache Cocoon 2.1.8-dev in 3 milliseconds. New format (an ISO8601-like): Processed by Apache Cocoon 2.1.8-dev in 0:00:03.612 Processed by Apach

Re: Right word for docs: cachability or cacheability

Thanks ben. It is committed. :-) Best Regards, Antonio Gallardo. On Dom, 1 de Mayo de 2005, 4:36, Ben Pope dijo: > Antonio Gallardo wrote: >> Can you send me a patch for a correct english of this? ;-) > > Apologies... > > That last patch was imcomplete. > > This covers all instances of cach(e)a

[EMAIL PROTECTED]: Project cocoon (in module cocoon) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project cocoon has an issue affecting its community integration. This issue affects 41 pr

Re: Right word for docs: cachability or cacheability

Antonio Gallardo wrote: Can you send me a patch for a correct english of this? ;-) Apologies... That last patch was imcomplete. This covers all instances of cach(e)ability, and replaces a with a to increase clarity. Ben Pope. Index: TraxTransformer.java ==

Re: Right word for docs: cachability or cacheability

Antonio Gallardo wrote: Thanks for the reply. This is the code in question: http://svn.apache.org/viewcvs.cgi/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/transformation/TraxTransformer.java?view=markup Used to generate this doc: http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/tra

Re: Right word for docs: cachability or cacheability

Thanks for the reply. This is the code in question: http://svn.apache.org/viewcvs.cgi/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/transformation/TraxTransformer.java?view=markup Used to generate this doc: http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/transformation/TraxTrans

Re: Right word for docs: cachability or cacheability

Antonio Gallardo wrote: Hi, I found a source that contains both words: cachability and cacheability I wonder wich one is the right. I guess the second is the right word. Please english native speakers tell me wich is the right one. In dictionary.com don't contain none of them and googling returns h

Right word for docs: cachability or cacheability

Hi, I found a source that contains both words: cachability and cacheability I wonder wich one is the right. I guess the second is the right word. Please english native speakers tell me wich is the right one. In dictionary.com don't contain none of them and googling returns hits for both. Only tha