Return-Path: 
 <dev-return-92187-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 84652 invoked from network); 11 Jan 2007 03:52:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 11 Jan 2007 03:52:24 -0000
Received: (qmail 63396 invoked by uid 500); 11 Jan 2007 03:52:29 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 63317 invoked by uid 500); 11 Jan 2007 03:52:29 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
List-Post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
List-Id: <dev.cocoon.apache.org>
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 63299 invoked by uid 99); 11 Jan 2007 03:52:29 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2007 19:52:29 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Received: from [70.168.83.81] (HELO centrmmtao03.cox.net) (70.168.83.81)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Jan 2007 19:52:19 -0800
Received: from eastrmimpo02.cox.net ([68.1.16.120]) by centrmmtao03.cox.net
          (InterMail vM.6.01.06.03 201-2131-130-104-20060516) with ESMTP
          id
 <20070111035158.PTSV13993.centrmmtao03.cox.net@eastrmimpo02.cox.net>
          for <dev@cocoon.apache.org>; Wed, 10 Jan 2007 22:51:58 -0500
Received: from [192.168.0.100] ([24.255.120.190])
	by eastrmimpo02.cox.net with bizsmtp
	id 9fqX1W00N46aSr40000000; Wed, 10 Jan 2007 22:50:31 -0500
Message-ID: <45A5B45A.9000108@reverycodes.com>
Date: Wed, 10 Jan 2007 22:51:54 -0500
From: Vadim Gritsenko <vadim@reverycodes.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Managing "changes" information
References: <459519FA.9080401@apache.org> <45951DEF.9020809@apache.org>
 <45958B53.4080505@dslextreme.com> <459CA990.3020305@apache.org>
 <459CAFA9.7050906@dslextreme.com> <459CB32D.3040207@apache.org>
 <459CBEC7.8030600@apache.org>
In-Reply-To: <459CBEC7.8030600@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Reinhard Poetz wrote:
> Reinhard Poetz wrote:
>> Ralph Goers wrote:
>>> Reinhard Poetz wrote:
>>>> Yes. Then I will setup the src/changes/changes.xml files in our 
>>>> modules because I guess that nobody wants to write a "StatusReport" 
>>>> module for Maven.
>>>> As I said before this solution comes with the downside that the 
>>>> description doesn't allow mixed content. Instead of having no 
>>>> changes reports this is acceptable ;-)
>>> What do you mean by "mixed content"?
>>>
>>
>> e.g. ordered lists --> <ol><li>foo</li><li>bar</ol>
>>
>> I looked into the sources of the Maven report generation mechanism and 
>> AFAICT this API makes it difficult (impossible?) to provide support 
>> for it.
> 
> see 
> http://cocoon.zones.apache.org/dev-docs/core-modules/core/2.2/changes-report.html. 
> The description of a particular change can only contain text.

This last change surely would be more readable if it was formatted with list or 
something.

Vadim