David Crossley wrote:
Ross Gardler wrote:
I will, just as soon as Cocoon head compiles again ;-)
No need to wait ...
cd cocoon-trunk
cp build.properties local.build.properties
... uncomment the two pairs of entries for "documentation" and "javadocs".
Cool, thanks.
Ross
--
No virus found in this ou
Ross Gardler wrote:
> I will, just as soon as Cocoon head compiles again ;-)
No need to wait ...
cd cocoon-trunk
cp build.properties local.build.properties
... uncomment the two pairs of entries for "documentation" and "javadocs".
--David
Rick Tessner wrote:
On Tue, 2005-01-11 at 12:47 +, Ross Gardler wrote:
Shall I do this locally, or shall I do it in our SVN. If I do it in SVN
I will ensure that I update it again if changes in Cocoon warrant such
work. Clearly I would prefer to do it in SVN as it will mean two new
plugins
On Tue, 2005-01-11 at 12:47 +, Ross Gardler wrote:
> Shall I do this locally, or shall I do it in our SVN. If I do it in SVN
> I will ensure that I update it again if changes in Cocoon warrant such
> work. Clearly I would prefer to do it in SVN as it will mean two new
> plugins available fo
Ross Gardler wrote:
...
Shall I do this locally, or shall I do it in our SVN.
If it does not break the normal site-generation functionalities that
Forrest publicizes, do it in SVN trunk. (my personal preference for this
particular thing)
If it's more unstable, do it on an SVN branch.
In any cas
SVN head of Cocoon has just introduced the ability to split cocoon.xconf
across multiple files. This will make the creation of more advanced
plugins much easier to manage. My current project requires the use of
the Authentication and Database blocks, both of which require changes to
cocoon.xcon
