You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Ross Gardler <rg...@apache.org> on 2005/01/11 13:47:44 UTC
Upgrade cocoon in 0.7-dev
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.xconf. I could do this work on a custom version of Forrest
locally, or I could upgrade the Cocoon version in SVN and make them plugins.
I've been watching the cocoon list and it seems the cocoon.xconf split
is currently working, but has problems with in some areas that we do not
use (forms for example).
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 for us (both only of use in a dynamic environment though).
Ross
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 10/01/2005
Re: Upgrade cocoon in 0.7-dev
Posted by Nicola Ken Barozzi <ni...@apache.org>.
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 case, do it in SVN :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Upgrade cocoon in 0.7-dev
Posted by Juan Jose Pablos <ch...@apache.org>.
Ross Gardler wrote:
> I've been watching the cocoon list and it seems the cocoon.xconf split
> is currently working, but has problems with in some areas that we do
> not use (forms for example).
>
> 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 for us (both only of use in a dynamic
> environment though).
>
I have the same thought, and I was waiting for their discussion to
finalize. Do it on SVN, we will help you if you get stuck (which I do
not think that will happend :-) )
Re: Upgrade cocoon in 0.7-dev
Posted by Juan Jose Pablos <ch...@apache.org>.
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".
>
>
>
or you could use the local.build.properties from here:
cheche@yarel:~/xml/forrest/trunk/etc/cocoon_upgrade$ ls local*
local.blocks.properties local.build.properties
Re: Upgrade cocoon in 0.7-dev
Posted by Ross Gardler <rg...@apache.org>.
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 outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 10/01/2005
Re: Upgrade cocoon in 0.7-dev
Posted by David Crossley <cr...@apache.org>.
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
Re: Upgrade cocoon in 0.7-dev
Posted by Ross Gardler <rg...@apache.org>.
Rick Tessner wrote:
> On Tue, 2005-01-11 at 12:47 +0000, 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 for us (both only of use in a dynamic environment though).
>
>
> I'd say "Go for it!" in the SVN trunk. :) If, in the unlikely event
> that it breaks existing Forrest functionality, it can be rolled back
> quite easily with SVN.
I will, just as soon as Cocoon head compiles again ;-)
Ross
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 10/01/2005
Re: Upgrade cocoon in 0.7-dev
Posted by Rick Tessner <ri...@apache.org>.
On Tue, 2005-01-11 at 12:47 +0000, 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 for us (both only of use in a dynamic environment though).
I'd say "Go for it!" in the SVN trunk. :) If, in the unlikely event
that it breaks existing Forrest functionality, it can be rolled back
quite easily with SVN.
At that point, a separate branch could be made for the split
cocoon.xconf implementation.
--
Rick Tessner
rick at apache dot org
RE: Upgrade cocoon in 0.7-dev
Posted by Alex Batlin <al...@batlin.com>.
Ross,
I have been able to add authentication and session blocks and created a
profiled/protected type of document. Here is the link :
http://www.batlin.com/devland/xmlpub/profiling.html. Hope that helps.
I was looking to create a plugin for this, once I get the hang of 07 and
cocoon.xconf splitting is done.
Regards,
Alex.
-----Original Message-----
From: Ross Gardler [mailto:rgardler@apache.org]
Sent: 11 January 2005 12:48
To: Forrest Developers List
Subject: Upgrade cocoon in 0.7-dev
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.xconf. I could do this work on a custom version of Forrest
locally, or I could upgrade the Cocoon version in SVN and make them plugins.
I've been watching the cocoon list and it seems the cocoon.xconf split
is currently working, but has problems with in some areas that we do not
use (forms for example).
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 for us (both only of use in a dynamic environment though).
Ross
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.10 - Release Date: 10/01/2005