From cocoonrandolphkayla@example.com Fri Dec 06 13:25:23 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 97526 invoked by uid 500); 6 Dec 2002 13:25:19 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 97468 invoked from network); 6 Dec 2002 13:25:17 -0000
Received: from mail.s-und-n.de (83.161.120.155)
  by daedalus.apache.org with SMTP; 6 Dec 2002 13:25:17 -0000
Received: from mail.s-und-n.de (localhost [83.161.120.155])
	by mail2.s-und-n.de (postfix) with ESMTP
	id 5F554895EF; Fri,  6 Dec 2002 14:25:12 +0100 (CET)
Received: from notes.sundn.de (ntsrv5.sundn.de [83.161.120.155])
	by mail.s-und-n.de (postfix) with ESMTP
	id 31EAA8955B; Fri,  6 Dec 2002 14:25:10 +0100 (CET)
Received: from hw0307 ([83.161.120.155])
          by notes.sundn.de (Lotus Domino Release 5.0.8)
          with SMTP id 2002120614250396:45105 ;
          Fri, 6 Dec 2002 14:25:03 +0100 
From: "Carsten Ziegeler" <randolphkayla@example.com>
To: "randolphkayla@example.com. Apache. Org" <randolphkayla@example.com>,
	<randolphkayla@example.com>,
	"Cocoon-Dev" <randolphkayla@example.com>,
	"Cocoon Docs" <randolphkayla@example.com>,
	"Cocoon-Users" <randolphkayla@example.com>
Subject: [ANN] Apache Cocoon 2.0.4 Release
Date: Fri, 6 Dec 2002 14:25:14 +0100
Message-ID: <randolphkayla@example.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June
 18, 2001) at 06.12.2002 14:25:03,
	Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at
 06.12.2002 14:25:06,
	Serialize randolphkayla@example.com 14:25:06
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Apache Cocoon 2.0.4 Released
----------------------------

   The Apache Cocoon team is proud to announce the new release
   of Apache Cocoon.


    Apache Cocoon is an XML framework that raises the usage of
    XML and XSLT technologies for server applications to a new level.
    Designed for performance and scalability around pipelined SAX
    processing, Cocoon offers a flexible environment based on the
    separation of concerns between content, logic and style.
    A centralized configuration system and sophisticated caching
    top this all off and help you to create, deploy and maintain
    rock-solid XML server applications.

    Today, most web engineers consider XML as the key for an improved
    web model and web site managers see XML as a way to reduce costs
    and ease production. In an era where services rather than software
    will be key for economic success, a better and less expensive model
    for web publishing will be a winner, especially one based on open
    standards.

    This release of Cocoon is a maintainance release focusing on
    improved performance and robustness. In addition some bugs were
    fixed and new features were added. See the following changes list
    for more information.



For more information about Apache Cocoon 2.0.4, please go to
http://xml.apache.org/cocoon

Changes with Apache Cocoon 2.0.4

*) The HTMLGenerator now accepts a JTidy configuration file for fine-grained
control on the generated document. [SW]

*) New Logicsheet for use with InputModules. [CH]

*) xsp.xsl now includes all xsp:init-page tags. Additional xsp:exit-page tag
for cleanup operations. [CH]

*) New InputModule to map parameter names to / from another name. Uses
translation table and additional prefix / suffix. [CH]

*) Fixed SimpleFormTransformer: Malformed XML with textarea elements.  [CH]

*) Allow to set the i18n transformer's locale from the sitemap as a
parameter (ported from 2.1-dev). The old behavior, based on LocaleAction is
preserved only for 2.0.x versions and will be removed from the further
releases (2.1 and higher). [KP]

*) New build target "validate-config" to conduct build-time validation of
some core important configuration files using RELAX NG (call it manually
with: ./build.sh validate-config). Currently doing: all sitemap.xmap, all
cocoon.roles, all *.xsl stylesheets, all book.xml files. [DC]

*) Extend the syntax of sitemap variable substitution : variables can have a
prefix which indicates an InputModule where to get the value from. For
example, the expression "{request-param:foo}" will evaluate to the value of
the "foo" request parameter (provided of course that the "request-param"
InputModule is correctly defined in cocoon.xconf). [SW]

*) RequestLifecycleComponents were not handled properly when the cocoon:
protocol is used [CZ]

*) Changed SimpleFormTransformer to use InputModules. [CH]

*) Changed InputModules to return Iterator instead of Enumeration. New
abstract "meta" module to make new meta modules easier. Stripped "meta" from
defaults module. Added JXPathMetaModule. Added extension classes and
packages to all modules that are based on JXPath. [CH]

*) Improved support for CLOB and BLOB columns in modular database actions.
[CH]

*) New chaining InputModule that allows to use additional modules when an
attribute is not present or null. [CH]

*) Changed defaults of InputModule names in many places to new names. [CH]

*) Fixing namespace handling of SQLTransformer. [CZ]

*) New ZipArchiveSerializer to build zip files aggregating various sources
as archive entries. Can be used to generate zip files, sxw files
(OpenOffice), jar files, etc. [SW]

*) TraxTransformer does not have use-deli parameter anymore. If deli is
configured in the cocoon.xconf, it always will be used. [VG]

*) CocoonServlet upload behavior now configurable from the web.xml.
Configuration parameters are: autosave-uploads, overwrite-uploads,
upload-max-size. See web.xml for description. [VG]

*) Remove the static factory variable in RequestFactory, and instead pass it
to the HttpRequest via the environment. [VG]

*) ReadDOMSessionTransformer now can work with any types of object (same
mechanism as in <xsp:expr> now used). Configuration parameter dom-name
renamed to attribute-name. [VG]

*) Src attribute can be used now with SessionAttributeGenerator to specify
session attribute name. Old syntax preserved. [VG]

*) Local parameters in SessionStateAction still do override global
parameters, but do NOT change global parameters. [VG]

*) Src attribute can be used now with ResourceExistsAction. Old parameter
syntax preserved. [VG]

*) Fixed prefix mapping for the sql transformer. [CZ]

*) FOP user configuration can now be specified as URL or relative path as
the value of the <user-config> element. [VG]

*) Load default FOP configuration only once, do not overwrite any user
configuration. [VG]

*) Remove unnessesary code in SVGBuilder. This also fixes intermittent
ClassCastExceptions in Batik code. [VG]

*) Fix issue with cross-platform uploads. Uploaded file's name converted to
match destination platform's path separator. [VG]

*) Absolute path now can be specified for work, cache, and upload directory.
Read comments in web.xml, and verify your settings. [VG]

*) Set URI resolver for XSLT handler every time time templates are used,
because XSLT templates might reference disposed instance of XSLT processor.
Fixes some NPEs in XSLT processor when templates cache is used. [VG]

*) Fix sitemap reloading bug: When parent sitemap is modified, it is
recompiled and reloaded. All sub-sitemaps of this sitemap also has to be
reloaded because they have references to the parent sitemap's
ComponentSelectors. This bug is the cause of some NPEs in the XSLT
processor. [VG]

*) Improve backward compatibility: FilePartFile needs toString() method to
work with code written for Cocoon 2.0. [VG]

*) AbstractServerPages used static fields for dependency tracking, which
caused either non-modified XSPs to be recompiled, or modified XSPs not to be
recompiled. [SW]

*) SearchGenerator now includes <field name=""/> elements into <hit/>
element. These elements contain stored fields of a found Document, making it
possible to provide additional info about document in the search result list
(only when index created with some stored fields). [VG]

*) In addition to attributes in same namespace with elements, link
serializer reacts on non-namespaced attributes too. This allows processing
of (strict) XHTML. [VG]

*) Backport usage of InputModules to compiled sitemap. [CH]

*) Sync modules and related components with HEAD. [CH]

*) Added some more types understood by modular database actions. [CH]

*) Request logicsheet: Fix session tags. [CH]

*) Added some more InputModules. [CH]

*) Changed existing OutputModules to not use ":" to separate key prefix from
suffix if prefix is an empty string. [CH]

*) Simple Formvalidation: FormValidatorAction sets attribute "*" to indicate
overall validation status. Added SimpleFormTransformer that fills XHTML form
fields with values from request parameters and allows conditional error tags
depending on validation result. This removes the requirement for XSP.
Changed ordering of error levels: "notpresent" (indicates that no validation
result is present for this parameter) moves between "ok" and "error". New
error level "maxerror" used in conjunction with the transformer, is never
set, used as upper bound. [CH]

*) (Modular) DatabaseActions: select produced wrong result if no rows were
found, query action returned broken result. [CH]

*) ESQL: Allow arbitrary types for prepared and callable statements via
dynamically loading classes like the SQLTransformer does. Is-null now uses
dynamic colum specification. Fixed skip-row feature, which was off by one.
Added tag to get connection meta data. [CH]

*) Fixed NPE in the recycling phase of content aggregation. [CZ]

*) Fixed bug in cocoon pseudo protocol involving aggregation of aggregated
resources spanning several sitemaps. [VG]

*) Conect to the XML:DB once, from the XMLDBSourceFactory. [VG]

*) <xsp-util:include-expr/> includes any object, converting it to string.
[VG]

*) XSP now verifies that value of attribute name on xsp:element does not
contains ':'. To create namespaced elements, uri and prefix attributes must
be used. [VG]

*) Request, response, and session logicsheet were incorrectly returning
result when as="xml" is specified. [VG]

*) XScript now has better variable management: variables of request,
session, global, and page scope are stored not in the XScriptManager, but as
request, session, context attributes, or as XSP page field (respectively).
Chances of memory leaks are highly reduced. [VG]

*) Include all warnings and errors reported by the XSLT engine into the
TransformerException if transformation fails or terminated by the
stylesheet. [VG]

*) Update HSQLDB to version 1.7.0. Now it properly shuts down with Cocoon.
[VG]

*) All log messages from FOP now go into the logs instead of printing them
to the screen. [CZ]

*) Applied patch for MaybeUploadRequestFactoryImpl which sets the timeout
for a session to infinite during an upload and restores it afterwards. [CZ]


The Cocoon Team
Carsten Ziegeler
Open Source Group, S&N AG


From cocoonrandolphkayla@example.com Mon Dec 09 21:34:21 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 68067 invoked by uid 500); 9 Dec 2002 21:34:21 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 68058 invoked from network); 9 Dec 2002 21:34:20 -0000
Received: from unknown (HELO dns.ascii27.net) (83.161.120.155)
  by daedalus.apache.org with SMTP; 9 Dec 2002 21:34:20 -0000
Received: from netarcana.com (localhost.localdomain [83.161.120.155])
	by dns.ascii27.net (8.12.1/8.12.1) with SMTP id gB9LYMxD014085
	for <randolphkayla@example.com>; Mon, 9 Dec 2002 16:34:23 -0500
Received: from 83.161.120.155
        (SquirrelMail authenticated user ajl)
        by netarcana.com with HTTP;
        Mon, 9 Dec 2002 16:34:23 -0500 (EST)
Message-ID: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>
Date: Mon, 9 Dec 2002 16:34:23 -0500 (EST)
Subject: Component Reference Pages...
From: "Andy Lewis" <randolphkayla@example.com>
To: <randolphkayla@example.com>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Reply-To: randolphkayla@example.com
X-Mailer: SquirrelMail (version 1.2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


Just verifying the status here -

- General consuensus that this is a good idea
- We have a format on the that seems like a good starting point
- The goal is to generate a lot of the info from JavaDoc style tags
- We don't curently have a JavaDoc generator to work with
- The Forrest transition is higher priority, and consuming the current focus

Please let me know if I'm missing something here. I am hoping to be able to pour some time into
this during the next couple of weeks. Does anyone have a starting point to use for a JavaDoc
generator?
Thanks!



-- 
"The heights of genius are only measurable by the depths of stupidity."



From cocoonrandolphkayla@example.com Tue Dec 10 07:07:45 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 73156 invoked by uid 500); 10 Dec 2002 07:07:45 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 73147 invoked from network); 10 Dec 2002 07:07:44 -0000
Received: from smtp-relay01.tc.dsvr.net (83.161.120.155)
  by daedalus.apache.org with SMTP; 10 Dec 2002 07:07:44 -0000
Received: from [83.161.120.155] (helo=codeconsult.dsvr.co.uk)
	by smtp-relay01.tc.dsvr.net with esmtp (Exim 3.33 #3)
	id 18LeUk-0005TK-00
	for randolphkayla@example.com; Tue, 10 Dec 2002 07:07:54 +0000
Received: from codeconsult.ch (lsb-catv-1-p211.vtxnet.ch [83.161.120.155])
	by codeconsult.dsvr.co.uk (8.11.6/8.11.6) with ESMTP id gBA77sP03703
	for <randolphkayla@example.com>; Tue, 10 Dec 2002 07:07:54 GMT
Message-ID: <randolphkayla@example.com>
Date: Tue, 10 Dec 2002 08:07:51 +0100
From: Bertrand Delacretaz <randolphkayla@example.com>
Organization: codeconsult
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1
X-Accept-Language: en
MIME-Version: 1.0
To: randolphkayla@example.com
Subject: Re: Component Reference Pages...
References: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi Andy,

As far as I know:

> - General consuensus that this is a good idea

yes.

> - We have a format on the that seems like a good starting point

on the wiki you mean?

There is
http://outerthought.net/wiki/Wiki.jsp?page=FileGeneratorManPage
which wasn't discussed much I think

and
http://outerthought.net/wiki/Wiki.jsp?page=CocoonDocsPlan
which seems to reflect the general consensus


> - The goal is to generate a lot of the info from JavaDoc style tags

Right, I think the followups to this message
http://marc.theaimsgroup.com/?l=xml-cocoon-docs&m=103788336715888&w=2
show agreement on this

> - We don't curently have a JavaDoc generator to work with

Right, see
http://marc.theaimsgroup.com/?l=xml-cocoon-docs&m=103796134326493&w=2#1
and followups, I don't think anyone is working on this right now.

> - The Forrest transition is higher priority, and consuming the current focus

Yes. I was meaning to write the JavaDocGenerator but other events 
prevented me from doing it.

>. . .Does anyone have a starting point to use for a JavaDoc
> generator?

Seems like using qdox (see http://qdox.sourceforge.net/usage.html for 
usage info) would make it fairly easy to generate javadoc SAX events 
from java source files. If you're not familiar with Generators, the 
source code of RequestGenerator would be a good example, as it also 
takes non-XML input.

Hope this helps!
-Bertrand


From cocoonrandolphkayla@example.com Tue Dec 10 10:18:16 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 8419 invoked by uid 500); 10 Dec 2002 10:18:15 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 8410 invoked from network); 10 Dec 2002 10:18:15 -0000
Received: from innocence.interface-business.de (83.161.120.155)
  by daedalus.apache.org with SMTP; 10 Dec 2002 10:18:15 -0000
Received: from rathole (rathole-srv.interface-business.de [83.161.120.155])
	by innocence.interface-business.de (8.12.6/8.12.6/ifb evision: 1.23 $) with SMTP id gBAAIRH1059142
	for <randolphkayla@example.com>; Tue, 10 Dec 2002 11:18:27 +0100 (CET)
	(envelope-from randolphkayla@example.com)
Received: from chuck.interface-business.de ([83.161.120.155]) by rathole; Tue, 10 Dec 2002 11:18:45 +0100 (MET)
Received: from interface-projects.de (dagobert.interface-business.de [83.161.120.155]) 	by chuck.interface-business.de (8.12.5/8.12.5) with ESMTP id gBAAIJRF067742 	for <randolphkayla@example.com>; Tue, 10 Dec 2002 11:18:20 +0100 (CET) 	(envelope-from randolphkayla@example.com)
Message-ID: <randolphkayla@example.com>
Date: Tue, 10 Dec 2002 11:18:19 +0100
From: Jens Lorenz <randolphkayla@example.com>
Organization: interface:projects
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.2.1) Gecko/20021130
X-Accept-Language: de-de, de, en-gb, en-us, en
MIME-Version: 1.0
To: randolphkayla@example.com
Subject: Re: Component Reference Pages...
References: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}> <randolphkayla@example.com>
In-Reply-To: <randolphkayla@example.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Bertrand Delacretaz wrote:

Hi Andy & Bertrand,

>> - The Forrest transition is higher priority, and consuming the current 
>> focus
> 
> 
> Yes. I was meaning to write the JavaDocGenerator but other events 
> prevented me from doing it.
> 
>> . . .Does anyone have a starting point to use for a JavaDoc
>> generator?
> 
> 
> Seems like using qdox (see http://qdox.sourceforge.net/usage.html for 
> usage info) would make it fairly easy to generate javadoc SAX events 
> from java source files. If you're not familiar with Generators, the 
> source code of RequestGenerator would be a good example, as it also 
> takes non-XML input.

Just to make you aware, I've been silently working on the Qdox generator 
approach.
(cause I really like the idea of having man page like reference 
documentation for the Cocoon components)

I've already a small command line tool working, which simply creates a 
DOM out of the data model of Qdox and writes this DOM to an XML file via 
Xerces.
I'm going to turn this into a (SAX-based) Cocoon generator as soon as 
time allows it (not before the holidays). I need a bit more time for this.

If you want to join in, you're welcome.

> Hope this helps!
> -Bertrand


Jens

-- 

Jens Lorenz

interface:projects GmbH                             \\|//
Tolkewitzer Strasse 49                              (o o)
01277 Dresden                               ~~~~oOOo~(_)~oOOo~~~~
Germany


From cocoonrandolphkayla@example.com Tue Dec 10 14:40:38 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 96516 invoked by uid 500); 10 Dec 2002 14:40:36 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 96500 invoked from network); 10 Dec 2002 14:40:36 -0000
Received: from unknown (HELO dns.ascii27.net) (83.161.120.155)
  by daedalus.apache.org with SMTP; 10 Dec 2002 14:40:36 -0000
Received: from netarcana.com (localhost.localdomain [83.161.120.155])
	by dns.ascii27.net (8.12.1/8.12.1) with SMTP id gBAEeNxD030892;
	Tue, 10 Dec 2002 09:40:24 -0500
Received: from 83.161.120.155
        (SquirrelMail authenticated user ajl)
        by netarcana.com with HTTP;
        Tue, 10 Dec 2002 09:40:26 -0500 (EST)
Message-ID: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>
Date: Tue, 10 Dec 2002 09:40:26 -0500 (EST)
Subject: Re: Component Reference Pages...
From: "Andy Lewis" <randolphkayla@example.com>
To: <randolphkayla@example.com>
In-Reply-To: <randolphkayla@example.com>
References: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>
        <randolphkayla@example.com>
        <randolphkayla@example.com>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Cc: <randolphkayla@example.com>
Reply-To: randolphkayla@example.com
X-Mailer: SquirrelMail (version 1.2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


<snip/>

> I've already a small command line tool working, which simply creates a  DOM out of the data
> model of Qdox and writes this DOM to an XML file via  Xerces.
> I'm going to turn this into a (SAX-based) Cocoon generator as soon as  time allows it (not
> before the holidays). I need a bit more time for this.

It sounds like you are most of the way there - stream to SAX, and wrap as a gernator should do it!
Very cool!>
> If you want to join in, you're welcome.

It does sound like I might be able to get to this before you can - where might I get acces to what
you have so far?
>
>> Hope this helps!

Yep - it rocks!


-- 
"The heights of genius are only measurable by the depths of stupidity."



From cocoonrandolphkayla@example.com Tue Dec 10 14:48:57 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 9526 invoked by uid 500); 10 Dec 2002 14:48:56 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 9515 invoked from network); 10 Dec 2002 14:48:56 -0000
Received: from unknown (HELO dns.ascii27.net) (83.161.120.155)
  by daedalus.apache.org with SMTP; 10 Dec 2002 14:48:56 -0000
Received: from netarcana.com (localhost.localdomain [83.161.120.155])
	by dns.ascii27.net (8.12.1/8.12.1) with SMTP id gBAEmsxD031325;
	Tue, 10 Dec 2002 09:48:54 -0500
Received: from 83.161.120.155
        (SquirrelMail authenticated user ajl)
        by netarcana.com with HTTP;
        Tue, 10 Dec 2002 09:48:55 -0500 (EST)
Message-ID: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>
Date: Tue, 10 Dec 2002 09:48:55 -0500 (EST)
Subject: Re: Component Reference Pages...
From: "Andy Lewis" <randolphkayla@example.com>
To: <randolphkayla@example.com>
In-Reply-To: <randolphkayla@example.com>
References: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>
        <randolphkayla@example.com>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Cc: <randolphkayla@example.com>
Reply-To: randolphkayla@example.com
X-Mailer: SquirrelMail (version 1.2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


>> - General consuensus that this is a good idea
>
> yes.

good

>
>> - We have a format on the that seems like a good starting point
>
> on the wiki you mean?

yes

>
> There is
> http://outerthought.net/wiki/Wiki.jsp?page=FileGeneratorManPage
> which wasn't discussed much I think
>

very true, but I'm not sure how to get more discussion of it - any ideas there?


> and
> http://outerthought.net/wiki/Wiki.jsp?page=CocoonDocsPlan
> which seems to reflect the general consensus
>

right...

>
>> - The goal is to generate a lot of the info from JavaDoc style tags
>
> Right, I think the followups to this message
> http://marc.theaimsgroup.com/?l=xml-cocoon-docs&m=103788336715888&w=2 show agreement on this

yep

>
>> - We don't curently have a JavaDoc generator to work with
>
> Right, see
> http://marc.theaimsgroup.com/?l=xml-cocoon-docs&m=103796134326493&w=2#1 and followups, I don't
> think anyone is working on this right now.
>
>> - The Forrest transition is higher priority, and consuming the current focus
>
> Yes. I was meaning to write the JavaDocGenerator but other events  prevented me from doing it.

understood...

>
>>. . .Does anyone have a starting point to use for a JavaDoc
>> generator?
>
> Seems like using qdox (see http://qdox.sourceforge.net/usage.html for  usage info) would make
> it fairly easy to generate javadoc SAX events  from java source files. If you're not familiar
> with Generators, the  source code of RequestGenerator would be a good example, as it also
> takes non-XML input.

thanks for the pointer - I have usually started with the FileGenerator and fill in from there. But
I'll take a look at the RequestGenerator too - this will be the first work I actually get to give
something real back to the community.
>
> Hope this helps!
> -Bertrand


-- 
"The heights of genius are only measurable by the depths of stupidity."



From cocoonrandolphkayla@example.com Tue Dec 10 15:11:50 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 35305 invoked by uid 500); 10 Dec 2002 15:11:49 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 35254 invoked from network); 10 Dec 2002 15:11:48 -0000
Received: from smtp-relay02.tc.dsvr.net (83.161.120.155)
  by daedalus.apache.org with SMTP; 10 Dec 2002 15:11:48 -0000
Received: from [83.161.120.155] (helo=codeconsult.dsvr.co.uk)
	by smtp-relay02.tc.dsvr.net with esmtp (Exim 3.34 #1)
	id 18Lm33-00008X-00
	for randolphkayla@example.com; Tue, 10 Dec 2002 15:11:49 +0000
Received: from codeconsult.ch (lsb-catv-1-p211.vtxnet.ch [83.161.120.155])
	by codeconsult.dsvr.co.uk (8.11.6/8.11.6) with ESMTP id gBAFBmA15410
	for <randolphkayla@example.com>; Tue, 10 Dec 2002 15:11:48 GMT
Message-ID: <randolphkayla@example.com>
Date: Tue, 10 Dec 2002 16:11:42 +0100
From: Bertrand Delacretaz <randolphkayla@example.com>
Organization: codeconsult
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1
X-Accept-Language: en
MIME-Version: 1.0
To: randolphkayla@example.com
Subject: Re: Component Reference Pages...
References: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>        <randolphkayla@example.com> <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Andy Lewis wrote:
 >. . .
>>There is
>>http://outerthought.net/wiki/Wiki.jsp?page=FileGeneratorManPage
>>which wasn't discussed much I think
>>
> very true, but I'm not sure how to get more discussion of it - any ideas there?

It might be that the draft is good enough at this stage, we probably 
need to be able to write some actual reference pages to get more feedback.

So if you and/or Jens are able to work on the JavadocGenerator, great! 
This will help us move forward on this. I will have very little time 
before January but will do my best to follow and give (hopefully 
meaningful) input.

-Bertrand


From cocoonrandolphkayla@example.com Wed Dec 11 12:48:21 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 54862 invoked by uid 500); 11 Dec 2002 12:48:21 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 54853 invoked from network); 11 Dec 2002 12:48:20 -0000
Received: from bender.bawue.de (83.161.120.155)
  by daedalus.apache.org with SMTP; 11 Dec 2002 12:48:20 -0000
Received: by bender.bawue.de (Postfix, from userid 10)
	id 299651B730; Wed, 11 Dec 2002 13:48:20 +0100 (MET)
Received: by mir (Postfix, from userid 1001)
	id 2C4716C585; Wed, 11 Dec 2002 13:47:40 +0100 (CET)
To: randolphkayla@example.com
Subject: Where to submit doc fixes?
From: Hans Ulrich Niedermann <randolphkayla@example.com>
Date: Wed, 11 Dec 2002 13:47:39 +0100
Message-ID: <randolphkayla@example.com>
User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.4 (Military
 Intelligence, i386-debian-linux)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

--=-=-=

Hi,

unfortunately I didn't find where/how to submit documentation fixes,
so I'm asking here now:

  - I read the documentation from CVS HEAD and didn't find it.

  - I tried to get information from <randolphkayla@example.com>,
    but ezmlm doesn't have any info about this list.

  - I tried to submit a bug in bugzilla, but there is no way to
    categorize a bug as documentation bug.

It's just a few little things, but if submitting patches is made too
difficult, one's mood tends to change towards "so what" :-)

Well, as the current traffic on this list currently doesn't seem to be
too much, I'll just attach my patches. It's nothing major, but still
stuff which should be fixed :-)

Uli


--=-=-=
Content-Type: text/x-patch
Content-Disposition: attachment; filename=modules.patch
Content-Description: Somebody forgot to embed the source in <source></source>.

Fixed source example formatting. 
Somebody forgot to embed the source in <source></source>.

Index: src/documentation/xdocs/userdocs/concepts/modules.xml
===================================================================
RCS file: /home/cvspublic/xml-cocoon2/src/documentation/xdocs/userdocs/concepts/modules.xml,v
retrieving revision 1.8
diff -u -3 -p -r1.8 modules.xml
--- src/documentation/xdocs/userdocs/concepts/modules.xml	5 Dec 2002 20:05:50 -0000	1.8
+++ src/documentation/xdocs/userdocs/concepts/modules.xml	11 Dec 2002 12:08:41 -0000
@@ -175,9 +175,11 @@
             The following example demonstrates the use of XPath function 
             with <code>system-property</code> module.
           </p>
+	  <source>
 <![CDATA[
     <map:parameter name="users-home-base" value="{system-property:substring-before(user.home, user.name)}"/>
 ]]>
+	  </source>
         </s3>
         <s3 title="Step 2b: Use it on an XSP">
           <p>

--=-=-=
Content-Type: text/x-patch
Content-Disposition: attachment; filename=nutshell.patch
Content-Description: nuthshell vs nutshell

Just a typo.

Index: src/documentation/xdocs/faq/faq-sitemap.xml
===================================================================
RCS file: /home/cvspublic/xml-cocoon2/src/documentation/xdocs/faq/faq-sitemap.xml,v
retrieving revision 1.8
diff -u -3 -p -r1.8 faq-sitemap.xml
--- src/documentation/xdocs/faq/faq-sitemap.xml	15 Nov 2002 13:36:23 -0000	1.8
+++ src/documentation/xdocs/faq/faq-sitemap.xml	11 Dec 2002 12:08:40 -0000
@@ -158,7 +158,7 @@
       to "no."
     </p>
 
-    <p>In a nuthsell: By default, reload is "asynchron" which means:</p>
+    <p>In a nutshell: By default, reload is "asynchron" which means:</p>
       <ol>
         <li>Change sitemap</li>
         <li>Hit reload</li>

--=-=-=
Content-Type: text/x-patch
Content-Disposition: attachment; filename=i18n-charset.patch
Content-Description: file was using different encoding than declared

This file contains UTF-8 encoded umlauts, but the encoding is
(wrongly) declared as latin1.

Index: src/documentation/xdocs/howto/howto-i18n-xmlform.xml
===================================================================
RCS file: /home/cvspublic/xml-cocoon2/src/documentation/xdocs/howto/howto-i18n-xmlform.xml,v
retrieving revision 1.4
diff -u -3 -p -r1.4 howto-i18n-xmlform.xml
--- src/documentation/xdocs/howto/howto-i18n-xmlform.xml	1 Nov 2002 13:46:18 -0000	1.4
+++ src/documentation/xdocs/howto/howto-i18n-xmlform.xml	11 Dec 2002 12:08:40 -0000
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
+<?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../dtd/document-v10.dtd">
 <document>
  <header>

--=-=-=--

From cocoonrandolphkayla@example.com Thu Dec 12 08:12:12 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 18688 invoked by uid 500); 12 Dec 2002 08:12:12 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 18679 invoked from network); 12 Dec 2002 08:12:12 -0000
Received: from ptolemy.goulburn.net.au (83.161.120.155)
  by daedalus.apache.org with SMTP; 12 Dec 2002 08:12:12 -0000
Received: (qmail 18128 invoked from network); 12 Dec 2002 08:12:23 -0000
Received: from max-02-048.goulburn.net.au (83.161.120.155)
  by ptolemy.goulburn.net.au with SMTP; 12 Dec 2002 08:12:23 -0000
Subject: Re: Where to submit doc fixes?
From: David Crossley <randolphkayla@example.com>
To: randolphkayla@example.com
In-Reply-To: <randolphkayla@example.com>
References: <randolphkayla@example.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) 
Date: 12 Dec 2002 19:12:21 +1100
Message-Id: <1039680742.2561.1791.camel@ighp>
Mime-Version: 1.0
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hans Ulrich Niedermann wrote:
> Hi,
> 
> unfortunately I didn't find where/how to submit documentation fixes,
> so I'm asking here now:
> 
>   - I read the documentation from CVS HEAD and didn't find it.

http://xml.apache.org/cocoon/howto/howto-bugzilla.html

>   - I tried to get information from <randolphkayla@example.com>,
>     but ezmlm doesn't have any info about this list.
> 
>   - I tried to submit a bug in bugzilla, but there is no way to
>     categorize a bug as documentation bug.

Just add [PATCH] to the front of the bug Summary line
and summarise what you are patching. Do not worry too much
about categorisation - we can figure it out if you just
describe it.

> It's just a few little things, but if submitting patches is made too
> difficult, one's mood tends to change towards "so what" :-)

That is right. We want it to be easy for everyone.

> Well, as the current traffic on this list currently doesn't seem to be
> too much, I'll just attach my patches. It's nothing major, but still
> stuff which should be fixed :-)
> 
> Uli

Thanks, i have applied your patches.
--David



From cocoonrandolphkayla@example.com Mon Dec 23 08:27:48 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 74403 invoked by uid 500); 23 Dec 2002 08:27:46 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 74393 invoked from network); 23 Dec 2002 08:27:46 -0000
Received: from sccrmhc01.attbi.com (83.161.120.155)
  by daedalus.apache.org with SMTP; 23 Dec 2002 08:27:46 -0000
Received: from k7.attbi.com (c-24-130-52-125.we.client2.attbi.com[83.161.120.155])
          by sccrmhc01.attbi.com (sccrmhc01) with SMTP
          id <20021223082758001003kdhle>; Mon, 23 Dec 2002 08:27:58 +0000
Message-Id: <randolphkayla@example.com>
X-Sender: randolphkayla@example.com
X-Mailer: QUALCOMM Windows Eudora Version 83.161.120.155
Date: Mon, 23 Dec 2002 00:26:07 -0800
To: randolphkayla@example.com
From: Ray Tayek <randolphkayla@example.com>
Subject: Configuring Environment - Java 1.4 configuration
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

at http://xml.apache.org/cocoon/installing/index.html under Configuring 
Environment - Java 1.4 configuration, it says to get xalan and xerces from 
lib/core. they seem to be in lib in cocoon-2.0.4.

also, it says:

"Due to changes in JDBC between JDK 1.3 and JDK 1.4, it is not possible to 
use Cocoon build on JDK 1.3 with JDK 1.4 when it comes to database 
connections.

So if you want to use Cocoon with JDK 1.4, you have to download the source 
distribution and build it by hand."

i would interpret this to mean the i can not use a cocoon built with jdk1.3 
on jdk1.4 if i want to use jdbc; but that if i do not need to use jdbc, 
then i am ok using a cocoon built with jdk1.3 on jdk1.4.

is this correct?

what version of jdk was cocoon-2.0.4 built with?

thanks

---
ray tayek http://home.attbi.com/~rtayek/ actively seeking mentoring or 
telecommuting work
vice chair orange county java users group http://www.ocjug.org/ 
mailto:randolphkayla@example.com
hate spam? http://samspade.org/ssw/


From cocoonrandolphkayla@example.com Thu Dec 26 13:58:04 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 77732 invoked by uid 500); 26 Dec 2002 13:58:03 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 77536 invoked from network); 26 Dec 2002 13:58:01 -0000
Received: from smtp2.a1.net (HELO smtp.a1.net) (83.161.120.155)
  by daedalus.apache.org with SMTP; 26 Dec 2002 13:58:01 -0000
Received: from a1.net (M960P029.adsl.highway.telekom.at [83.161.120.155])
 by smtp2.a1.net (iPlanet Messaging Server 5.1 HotFix 0.9 (built May 30 2002))
 with ESMTPA id <randolphkayla@example.com> for randolphkayla@example.com;
 Thu, 26 Dec 2002 14:58:01 +0100 (MET)
Date: Thu, 26 Dec 2002 14:58:11 +0100
From: Bernhard Huber <randolphkayla@example.com>
Subject: [STATUS] qdox  java generator
To: randolphkayla@example.com
Message-id: <randolphkayla@example.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2)
 Gecko/20021126
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

hi,

i have some time building a JavaDocGenerator using qdox,
qdox is really very simple.
i plan just to marrshal qdox objects to xml using
ns xmlns:jd="http://org.apache/cocoon/javadoc/1.0".

all other transfromation should be done by some transformations
steps down the pipeline.

First I tried to use Castor, but Castor wants always getXXX() too,
which are not always available int QDOX classes.
Thus I do the marshalling manually.

it's not finished yet, still some way to go, ....

regards bernhard

a xml generator snippet of JavDocGenerator:
<?xml version="1.0"?>
<jd:javadoc xmlns:jd="http://org.apache/cocoon/javadoc/1.0">
<jd:javadoc>
....
<jd:java-source 
file="\projects\external-java-projects\cocoon-homepage\src\java\org\apache\cocoon\generation\javadoc\JavaDocGenerator.java" 
package="org.apache.cocoon.generation.javadoc">
<jd:imports>org.apache.avalon.framework.parameters.Parameters</jd:imports>
....
<jd:java-class>org.apache.cocoon.generation.javadoc.JavaDocGenerator</jd:java-class>
</jd:java-source>

<jd:java-class 
fully-qualified-name="org.apache.cocoon.generation.javadoc.JavaDocGenerator" 

package="org.apache.cocoon.generation.javadoc" is-interface="false" 
is-public="true">
...
<jd:comment>Description of the Class</jd:comment>
<jd:doclet-tag name="author" value="Administrator">
   <jd:parameter key="Administrator" value=""/>
</jd:doclet-tag>
...
<jd:super-class key="$Id$" 
value="">org.apache.cocoon.generation.ComposerGenerator</jd:super-class>

</jd:java-class>
.......


From cocoonrandolphkayla@example.com Thu Dec 26 21:17:45 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 64012 invoked by uid 500); 26 Dec 2002 21:17:45 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 64003 invoked from network); 26 Dec 2002 21:17:44 -0000
Received: from unknown (HELO dns.ascii27.net) (83.161.120.155)
  by daedalus.apache.org with SMTP; 26 Dec 2002 21:17:44 -0000
Received: from netarcana.com (localhost.localdomain [83.161.120.155])
	by dns.ascii27.net (8.12.1/8.12.1) with SMTP id gBQLHixD009094;
	Thu, 26 Dec 2002 16:17:45 -0500
Received: from 83.161.120.155
        (SquirrelMail authenticated user ajl)
        by netarcana.com with HTTP;
        Thu, 26 Dec 2002 16:17:45 -0500 (EST)
Message-ID: <{{EMAIL+SOCIAL_SECURITY_NUMBER}}>
Date: Thu, 26 Dec 2002 16:17:45 -0500 (EST)
Subject: Re: [STATUS] qdox  java generator
From: "Andy Lewis" <randolphkayla@example.com>
To: <randolphkayla@example.com>
In-Reply-To: <randolphkayla@example.com>
References: <randolphkayla@example.com>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
Cc: <randolphkayla@example.com>
Reply-To: randolphkayla@example.com
X-Mailer: SquirrelMail (version 1.2.6)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


I just sent off to Jens the work I have done on his version. It uses QDox also, no castor, but
goes straight to SAX. It works...but I'd rather Jens gets to take a look first...
> hi,
>
> i have some time building a JavaDocGenerator using qdox,
> qdox is really very simple.
> i plan just to marrshal qdox objects to xml using
> ns xmlns:jd="http://org.apache/cocoon/javadoc/1.0".
>
> all other transfromation should be done by some transformations
> steps down the pipeline.
>
> First I tried to use Castor, but Castor wants always getXXX() too, which are not always
> available int QDOX classes.
> Thus I do the marshalling manually.
>
> it's not finished yet, still some way to go, ....
>
> regards bernhard
>
> a xml generator snippet of JavDocGenerator:
> <?xml version="1.0"?>
> <jd:javadoc xmlns:jd="http://org.apache/cocoon/javadoc/1.0">
> <jd:javadoc>
> ....
> <jd:java-source
> file="\projects\external-java-projects\cocoon-homepage\src\java\org\apache\cocoon\generation\javadoc\JavaDocGenerator.java">  package="org.apache.cocoon.generation.javadoc">
> <jd:imports>org.apache.avalon.framework.parameters.Parameters</jd:imports> ....
> <jd:java-class>org.apache.cocoon.generation.javadoc.JavaDocGenerator</jd:java-class>
> </jd:java-source>
>
> <jd:java-class
> fully-qualified-name="org.apache.cocoon.generation.javadoc.JavaDocGenerator"
>
> package="org.apache.cocoon.generation.javadoc" is-interface="false"  is-public="true">
> ...
> <jd:comment>Description of the Class</jd:comment>
> <jd:doclet-tag name="author" value="Administrator">
>   <jd:parameter key="Administrator" value=""/>
> </jd:doclet-tag>
> ...
> <jd:super-class key="$Id$"
> value="">org.apache.cocoon.generation.ComposerGenerator</jd:super-class>
>
> </jd:java-class>
> .......


-- 
"The heights of genius are only measurable by the depths of stupidity."



From cocoonrandolphkayla@example.com Sat Dec 28 14:30:31 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 62853 invoked by uid 500); 28 Dec 2002 14:30:29 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 62823 invoked from network); 28 Dec 2002 14:30:28 -0000
Received: from eos.telenet-ops.be (83.161.120.155)
  by daedalus.apache.org with SMTP; 28 Dec 2002 14:30:28 -0000
Received: from localhost (localhost.localdomain [83.161.120.155])
	by eos.telenet-ops.be (Postfix) with SMTP
	id C6AB22149D; Sat, 28 Dec 2002 15:30:29 +0100 (CET)
Received: from outerthought.org (D5E00A87.kabel.telenet.be [83.161.120.155])
	by eos.telenet-ops.be (Postfix) with ESMTP
	id 6087721CF1; Sat, 28 Dec 2002 15:30:29 +0100 (CET)
Message-ID: <randolphkayla@example.com>
Date: Sat, 28 Dec 2002 15:30:29 +0100
From: Steven Noels <randolphkayla@example.com>
Organization: Outerthought
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en
MIME-Version: 1.0
To: randolphkayla@example.com
Cc: randolphkayla@example.com, randolphkayla@example.com
Subject: Re: [warning] Wiki being moved
References: <randolphkayla@example.com>
In-Reply-To: <randolphkayla@example.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Steven Noels wrote:

> I'm moving the Wiki to its new location on 
> http://wiki.cocoondev.org/

I'll quit fussing around for now - did some Forrestizing along the way. 
I didn't really pay much attention on validity of the generated HTML, 
and only checked in Moz1.2 and IE6 on W2K. If anyone has big problems 
reading the Wiki, please let me know.

Enjoy,

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at              http://radio.weblogs.com/0103539/
randolphkayla@example.com                randolphkayla@example.com


From cocoonrandolphkayla@example.com Tue Dec 31 08:38:57 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 66024 invoked by uid 500); 31 Dec 2002 08:38:57 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 66012 invoked from network); 31 Dec 2002 08:38:56 -0000
Received: from tartarus.telenet-ops.be (83.161.120.155)
  by daedalus.apache.org with SMTP; 31 Dec 2002 08:38:56 -0000
Received: from localhost (localhost.localdomain [83.161.120.155])
	by tartarus.telenet-ops.be (Postfix) with SMTP id E40F6DBA1C
	for <randolphkayla@example.com>; Tue, 31 Dec 2002 09:39:08 +0100 (CET)
Received: from outerthought.org (D5E00A87.kabel.telenet.be [83.161.120.155])
	by tartarus.telenet-ops.be (Postfix) with ESMTP id B4E0FDC7AF
	for <randolphkayla@example.com>; Tue, 31 Dec 2002 09:39:08 +0100 (CET)
Message-ID: <randolphkayla@example.com>
Date: Tue, 31 Dec 2002 09:39:08 +0100
From: Steven Noels <randolphkayla@example.com>
Organization: Outerthought
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en
MIME-Version: 1.0
To: randolphkayla@example.com
Subject: Out of which branch should the website be published?
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hm.

David was looking off-list into some issues with the website, and I was 
trying to help.

Currently, I have a check-out of:

  - cocoon_2_0_3 branch
  - cocoon_2_0_4 branch
  - HEAD

on my machine, but I fail to see how we can consistently decide which 
branch (or HEAD) should go on the public website.

  - news.xml of the HEAD branch contains relevant info
  - some docs in the HEAD branch are not pertinent for the public 
website (non-release-version docs)
  - what about the 2_0_3/2_0_4 branch?
    - 2_0_4 contains recent changes (at least from Sylvain)
    - 2_0_3 has been the focal point of David's efforts lately

Maybe all this might become more clear if we

  - isolate docs into their own CVS module (yes, I know this has been 
suggested before - I believe the complexity and volume of Cocoon doco 
warrants this, and requires some dedication to sort out where to commit 
what)
  - maintain a branch LIVE_WEBSITE over there?

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at              http://radio.weblogs.com/0103539/
randolphkayla@example.com                randolphkayla@example.com


From cocoonrandolphkayla@example.com Tue Dec 31 09:04:54 2002
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 74724 invoked by uid 500); 31 Dec 2002 09:04:53 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 74713 invoked from network); 31 Dec 2002 09:04:52 -0000
Received: from tartarus.telenet-ops.be (83.161.120.155)
  by daedalus.apache.org with SMTP; 31 Dec 2002 09:04:52 -0000
Received: from localhost (localhost.localdomain [83.161.120.155])
	by tartarus.telenet-ops.be (Postfix) with SMTP id 12EBFDBF97
	for <randolphkayla@example.com>; Tue, 31 Dec 2002 10:05:05 +0100 (CET)
Received: from outerthought.org (D5E00A87.kabel.telenet.be [83.161.120.155])
	by tartarus.telenet-ops.be (Postfix) with ESMTP id DA663DC194
	for <randolphkayla@example.com>; Tue, 31 Dec 2002 10:05:04 +0100 (CET)
Message-ID: <randolphkayla@example.com>
Date: Tue, 31 Dec 2002 10:05:04 +0100
From: Steven Noels <randolphkayla@example.com>
Organization: Outerthought
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en
MIME-Version: 1.0
To: randolphkayla@example.com
Subject: Re: Out of which branch should the website be published?
References: <randolphkayla@example.com>
In-Reply-To: <randolphkayla@example.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Steven Noels wrote:

> Currently, I have a check-out of:
> 
>  - cocoon_2_0_3_branch
>  - cocoon_2_0_4 tagged files (not a branch!)
                   ^^^^^^

>  - HEAD
> 
> on my machine, but I fail to see how we can consistently decide which 
> branch (or HEAD) should go on the public website.
> 
>  - news.xml of the HEAD branch contains relevant info
>  - some docs in the HEAD branch are not pertinent for the public website 
> (non-release-version docs)
>  - what about the 2_0_3/2_0_4 branch?
>    - 2_0_4 contains recent changes (at least from Sylvain)

wrong

>    - 2_0_3 has been the focal point of David's efforts lately

no branch has been created after the 2.0.4 release

> Maybe all this might become more clear if we
> 
>  - isolate docs into their own CVS module (yes, I know this has been 
> suggested before - I believe the complexity and volume of Cocoon doco 
> warrants this, and requires some dedication to sort out where to commit 
> what)
>  - maintain a branch LIVE_WEBSITE over there?
> 
> </Steven>

My bad,

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at              http://radio.weblogs.com/0103539/
randolphkayla@example.com                randolphkayla@example.com


From cocoonrandolphkayla@example.com Wed Jan 01 03:07:53 2003
Return-Path: <cocoonrandolphkayla@example.com>
Delivered-To: randolphkayla@example.com
Received: (qmail 89519 invoked by uid 500); 1 Jan 2003 03:07:53 -0000
Mailing-List: contact randolphkayla@example.com; run by ezmlm
Precedence: bulk
list-help: <mailto:randolphkayla@example.com>
list-unsubscribe: <mailto:randolphkayla@example.com>
list-post: <mailto:randolphkayla@example.com>
Reply-To: randolphkayla@example.com
Delivered-To: mailing list randolphkayla@example.com
Received: (qmail 89510 invoked from network); 1 Jan 2003 03:07:52 -0000
Received: from ptolemy.goulburn.net.au (83.161.120.155)
  by daedalus.apache.org with SMTP; 1 Jan 2003 03:07:52 -0000
Received: (qmail 18316 invoked from network); 1 Jan 2003 03:08:00 -0000
Received: from max-02-017.goulburn.net.au (83.161.120.155)
  by ptolemy.goulburn.net.au with SMTP; 1 Jan 2003 03:08:00 -0000
Subject: Re: Out of which branch should the website be published?
From: David Crossley <randolphkayla@example.com>
To: randolphkayla@example.com
In-Reply-To: <randolphkayla@example.com>
References: <randolphkayla@example.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) 
Date: 01 Jan 2003 14:07:59 +1100
Message-Id: <1041390480.19591.111.camel@ighp>
Mime-Version: 1.0
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Steven Noels wrote: 
<snip/>
> but I fail to see how we can consistently decide which 
> branch (or HEAD) should go on the public website.

I have already noted this at issue #19 on the Wiki
http://wiki.cocoondev.org/Wiki.jsp?page=ForrestProposal
------
19. From which branch does the website get generated - head or
release branch?
READER COMMENTS
 1. (dc) It is currently generated from the release branch.
Those xdocs are meant to be always in sync with the head of CVS.
The documentation does describe the head of CVS and we do not
maintain any separate "release" version of the docs (rather we
put notes in the documentation to indicate which branch applies).
So why do we not generate the website from the head of CVS?
The only reason that i can think of is that the "changes.html"
on the website describes the current release branch and not
all relevant changes to head have gone into release branch, so
the "changes" documents are necessarily different
------

>   - news.xml of the HEAD branch contains relevant info

That should be in sync with the release branch.

>   - some docs in the HEAD branch are not pertinent for the public 
> website (non-release-version docs)

No. We decided some time back not to maintain separate
versions of docs but to just note at the top of the doc
if it pertained to a certain branch. 

>   - what about the 2_0_3/2_0_4 branch?
>     - 2_0_4 contains recent changes (at least from Sylvain)
>     - 2_0_3 has been the focal point of David's efforts lately

As already discussed, there is only HEAD and
release branch, though the latter should actually
be called just "cocoon_2_0_branch".

> Maybe all this might become more clear if we
> 
>   - isolate docs into their own CVS module (yes, I know this has been 
> suggested before - I believe the complexity and volume of Cocoon doco 
> warrants this, and requires some dedication to sort out where to commit 
> what)

There is a big problem with people not also committing
doc changes into the release branch (only head). Yes this
is discouraging and a separate cvs module might help.

Did we decide something in that previous discussion
and did we look at the associated issues? I cannot
find the original thread.

>   - maintain a branch LIVE_WEBSITE over there?

How will that help? We already have problems with
branch management.

--David




{'source': 'Apache Software Foundation Public Mail Archives'}