> From: Stuart Roebuck (Telewest) [mailto:[EMAIL PROTECTED]]
>
> Thanks Vadim,
>
> Up until now I've happily gotten away with merging changes to the
> src/webapp/cocoon.xconf into my own when updating my Cocoon version -
> it's clear that I should have used the build version of the document
> which isn't the same thing any more!
And this "any more" is here for a quite a while now:
Wed Jan 16 10:39:22 2002 UTC (7 weeks, 6 days ago) by cziegeler:
Added new XConfTool which dynamically adds
blocks to the cocoon.xconf. This is similar
to the sitemap tool, but less sophisticated...for now
:)
> This reminds me - how about having a plaintext "WHATSNEW" file at the
> CVS root to which everyone appends changes (in reverse date order -
with
> clearly titled break lines for releases), listing any changes to
Cocoon
> that impact on the configuration, plus anything else that may be of
> general interest like 'implemented XXX which speeds up Cocoon by a
> factor of 100'.
This is called "changes.xml". Sample record:
<action dev="CZ" type="update">
Restructured build system. A new ant task (SitemapToolTask) adds
entries
of optional components to the sitemap. Warnings for not available
optional components are printed out.
</action>
(I must confess: for second version of XConfTool I did not wrote entry
to changes.xml, I only sent [ANNOUNCEMENT] email)
> It would be *extremely* helpful if someone maintaining a Cocoon
> configuration could work on the basis that an update of Cocoon would
> work with their existing .xconf and .xmap files unless explicitly
> indicated in the WHATSNEW file.
>
> I don't think this would be hard to maintain, and it would make it
> easier to construct release notes to encourage interest in the latest
> and greatest releases. The Ant project does it quite well.
Isn't current Cocoon's release notes are constructed from the
changes.xml?
Vadim
> Stuart.
>
> On Tuesday, March 12, 2002, at 06:41 pm, Vadim Gritsenko wrote:
>
> >> From: Stuart Roebuck [mailto:[EMAIL PROTECTED]]
> >>
> >> What is the xconf tool?
> >
> > From build.xml:
> > ---------
> > <!-- A task to change the xconf. It is used to add optional
> > components -->
> > <taskdef name="xconf-tool" classname="XConfToolTask"
> > classpath="${tools.dir}/anttasks"/>
> >
> > <!-- Invoke the XConfTool to add optional entries -->
> > <xconf-tool directory="${build.src}"
> > extension="xmap"
> > configuration="${build.war}/sitemap.xmap"/>
> >
> > <xconf-tool directory="${build.src}"
> > extension="xpipe"
> > configuration="${build.war}/sitemap.xmap"/>
> >
> > <xconf-tool directory="${build.src}"
> > extension="xconf"
> > configuration="${build.war}/cocoon.xconf"/>
> > ---------
> >
> > From pizza.xconf:
> > ---------
> > <?xml version="1.0"?>
> >
> > <xconf xpath="cocoon/programming-languages/java-language"
> > unless="parameter[@name='compiler']">
> > <!-- Compiler parameter specifies which class to use to
compile
> > Java.
> > Possible variants are:
> > Javac. Requires javac.jar (included with JDK as
> > lib/toools.jar).
> > Pizza. Requires pizza.jar (included with Cocoon
> > distribution).
> > Jikes. Requires IBM jikes compiler to be present in the
> > PATH -->
> > <parameter name="compiler"
> >
value="org.apache.cocoon.components.language.programming.java.Pizza"/>
> > </xconf>
> > ---------
> >
> > Vadim
> >
>
> Public Key - 1024D/88DD65AF 2001-11-23 Stuart Roebuck
(Adolos)
> Key fingerprint = 89D9 E405 F8B1 9B22 0FA2 F2C1 9E57 5AB1 88DD
65AF
>
------------------------------------------------------------------------
-
> Stuart Roebuck
[EMAIL PROTECTED]
> Systems Architect Java, XML, MacOS X, XP,
> etc.
> ADOLOS
<http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
