Juan Jose Pablos wrote:
> Alex,
> If you want to use forrest 0.6 then you need to get cocoon 2.1.5 from:
>
> http://archive.apache.org/dist/cocoon/
Or you can probably use their release branch of cocoon/branches/BRANCH_2_1_X
which is known as cocoon-2_1_X
A certain SVN revision of their cocoon/trunk (i.e. cocoon-2.2) is what we
use in our Forrest trunk (i.e. forrest-0.7-dev). Look in our lib/ directory
for the name of their cocoon-*.jar filenames to indicate which SVN revision
that we used.
--David
> If you use svn version for both (forrest and cocoon) , there is a higher
> change that we can help you, and any bug that you find is fixed for the
> next released.
>
> It is up to you.. but I would go for option 2
>
> Cheers,
> Cheche
>
> Alex Batlin wrote:
>
> >Hi rick,
> >
> >I am getting on with the task, but got confused with which version of
> >cocoon
> >to use. I co first 2.1.5 as looking at release notes for forrest 0.6 cocoon
> >2.1.5 is used. However doing a build shows that cocoon 2.2.0-dev is used.
> >This I cannot seem to find in the SVN repository. Which branch/tag should I
> >be using. Many thanks
> >
> >
> >Alex.
> >
> >-----Original Message-----
> >From: Rick Tessner [mailto:rick@apache.org]
> >Sent: 10 December 2004 17:55
> >To: dev@forrest.apache.org
> >Subject: Re: Dynamic or Static Access Control Lists
> >
> >Alex Batlin wrote:
> >
> >
> >>I posted this a few days ago, I wonder if it was missed?
> >>
> >>I have had a look more at how document profiling can be done with some of
> >>the suggestions included:
> >>
> >>1. created profile-docbook2document.xsl that only includes sections of
> >>docbook docs that match attribute userrole to one set in a parameter 2.
> >>created sitemap.xmap pipeline to transform so far a test document using
> >>
> >>
> >this
> >
> >
> >>new xsl and pass the userrole parameter in the transform 3. I now need to
> >>set up an authentication pipeline, here are the docs I
> >>found:
> >>
> >>http://cocoon.apache.org/2.1/developing/webapps/authentication.html
> >>
> >>however when I try to add the auth actions, forrest complains that such
> >>actions are not defined. Looking at the cocoon dist, these actions are
> >>included in one of the blocks dirs (whatever that means), but cannot find
> >>them in forrest.
> >>
> >>Can anyone help me understand how I can use the auth actions in my
> >>
> >>
> >sitemap?
> >
> >
> >>Does forrest come with a stripped down version of cocoon, if so how do I
> >>install the actions or does forrest 0.7 solve this?
> >>
> >>
> >
> >Not sure if this'll work (haven't tried it). This is based purely on what
> >I see in the cocoon blocks.properties
> >
> >1. Check out cocoon from SVN.
> >2. Copy the local.blocks.properties and local.build.properties from
> >$FORREST_HOME/etc/cocooon_upgrade to the cocoon top-level directory.
> >3. Edit the local.blocks.properties to change
> > include.block.authentication-fw to true
> > include.block.session-fw to true
> >4. Build cocoon by running "build.sh" in the cocoon top-level directory.
> >5. Copy the
> >$COCOON_HOME/build/cocoon-2.2.0-dev/blocks/authentication*-block.jar to
> >$FORREST_HOME/lib/optional/
> >6. Try it with a "forrest run"
> >
> >Let the list know how it goes.
> >
> >
> >
> >