Re: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
Grzegorz Kossakowski wrote: Joerg Heinicke pisze: joerg wrote: Modified: cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml Could it be we switched from status.xml to changes.xml? :) Yes, I believe so. I haven't touch any status.xml since I'm committer and nobody complained to date. :) There are still 100 status.xml in trunk. Before I clean them up I want to know if that's correct. File changes.xml is supported by Maven reporting plug-in[1]. I don't know anything about a tool supporting status.xml in trunk so you can be almost sure we have switched. [1] http://maven.apache.org/plugins/maven-changes-plugin/ The status.xml files were used when Forrest generated the Cocoon docs for both 2.1 and trunk. They should still be used for all 2.1 changes. When trunk docs were moved to using Maven, some people kept adding to */status.xml as there was no replacement for generating changes. Now the 2.2 status.xml files need to be migrated. -David
Re: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
Joerg Heinicke pisze: On 12.01.2008 21:20, [EMAIL PROTECTED] wrote: Modified: cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml Could it be we switched from status.xml to changes.xml? :) Yes, I believe so. I haven't touch any status.xml since I'm committer and nobody complained to date. :) There are still 100 status.xml in trunk. Before I clean them up I want to know if that's correct. File changes.xml is supported by Maven reporting plug-in[1]. I don't know anything about a tool supporting status.xml in trunk so you can be almost sure we have switched. [1] http://maven.apache.org/plugins/maven-changes-plugin/ -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/
Re: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
Joerg Heinicke wrote:
On 12.01.2008 21:20, [EMAIL PROTECTED] wrote:
Modified:
cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
Could it be we switched from status.xml to changes.xml? :)
yes. We had some discussion about it when I switched our doc generation to be
based on Maven 2. The only disadvantage is that changes.xml only allows text in
the description element and not mixed content. I tried to fix it in the Maven
Changes plugin but without success :-(
--
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: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
Reinhard Poetz pisze: Joerg Heinicke wrote: On 12.01.2008 21:20, [EMAIL PROTECTED] wrote: Could it be we switched from status.xml to changes.xml? :) yes. We had some discussion about it when I switched our doc generation to be based on Maven 2. The only disadvantage is that changes.xml only allows text in the description element and not mixed content. I tried to fix it in the Maven Changes plugin but without success :-( It's not entirely true. You can use CDATA section and put HTML tags into it. See[1] [1] http://jira.codehaus.org/browse/MCHANGES-9 -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/
Re: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
Grzegorz Kossakowski wrote:
Reinhard Poetz pisze:
Joerg Heinicke wrote:
On 12.01.2008 21:20, [EMAIL PROTECTED] wrote:
Could it be we switched from status.xml to changes.xml? :)
yes. We had some discussion about it when I switched our doc generation to
be based on Maven 2. The only disadvantage is that changes.xml only allows
text in the description element and not mixed content. I tried to fix it in
the Maven Changes plugin but without success :-(
It's not entirely true. You can use CDATA section and put HTML tags into it.
See[1]
great! It's not as comfortable as in status.xml files but at least a work around
that is good enough :-)
--
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: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
On 13.01.2008 05:17, Grzegorz Kossakowski wrote: cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml Could it be we switched from status.xml to changes.xml? :) Yes, I believe so. I haven't touch any status.xml since I'm committer and nobody complained to date. :) For me it is the other way around. I still have put all changes into status.xml and nobody complained :) Joerg
Re: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
Joerg Heinicke pisze: On 13.01.2008 05:17, Grzegorz Kossakowski wrote: cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml Could it be we switched from status.xml to changes.xml? :) Yes, I believe so. I haven't touch any status.xml since I'm committer and nobody complained to date. :) For me it is the other way around. I still have put all changes into status.xml and nobody complained :) Hehe, funny :) I must have missed that so I didn't ask earlier. Anyway, Reinhard dissipated any doubts. -- Grzegorz Kossakowski Committer and PMC Member of Apache Cocoon http://reflectingonthevicissitudes.wordpress.com/
Re: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
On 13.01.2008 09:30, Grzegorz Kossakowski wrote: You can use CDATA section and put HTML tags into it. See[1] It's a pain that they disable output escaping! Why not allowing free markup? Wherever we put escaped markup into our changes to show them to the user they will end up as markup in the actual HTML - and screw up the page. Joerg
Re: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
On 13.01.2008 09:20, Reinhard Poetz wrote: Could it be we switched from status.xml to changes.xml? :) yes. We had some discussion about it when I switched our doc generation to be based on Maven 2. I'm going to move changes put into status.xml to corresponding changes.xml and get rid of status.xml. It was only me and Carsten who still used status.xml :) One is different though. There is a status.xml in commons directory and I don't see a corresponding changes.xml. What about it? Joerg
Re: svn commit: r611525 - /cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml
On 12.01.2008 21:20, [EMAIL PROTECTED] wrote: Modified: cocoon/trunk/blocks/cocoon-imageop/cocoon-imageop-impl/src/changes/changes.xml Could it be we switched from status.xml to changes.xml? :) There are still 100 status.xml in trunk. Before I clean them up I want to know if that's correct. Joerg
