cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Billard" <obill...@rennes.jouve.fr>
Subject Re: How to keep own sitemap clean between CVS updates ?
Date Thu, 22 May 2003 07:58:25 GMT
Hi Giacomo,

I reposted the mail because I only sent it to you the first time...
Sorry if it appeared to you as a lack of trust ! :) I didn't received your
answer before reposting.

I'm less-than-6-month new to Cocoon, and I don't know the best manner to
developp a webapp with cocoon, and to use Ant to do this. And the Cocoon-doc
doesn't seems to talk about it, but maybe haven't I read all this stuff...

What I'm doing is have a dev-webapp folder where I point the JETTY_WEBAPP
var. It's quick to change the sitemap or any file, but it's true that it's
not the best way to go.

So what you suggest is to have a dev folder for the project, and add an ant
task for copying the project files in the build/webapp folder ?
But isn't it a little bit boring to run a build anytime you modify your
sitemap or other files ?
Is that the way your working ? I'm curious to know more about it.

Thanks again for your answer !

--
Olivier

----- Original Message ----- 
From: "Giacomo Pati" <giacomo@apache.org>
To: <cocoon-users@xml.apache.org>; "Olivier Billard" <obillard@jouve.fr>
Sent: Wednesday, May 21, 2003 9:35 PM
Subject: Re: How to keep own sitemap clean between CVS updates ?


> On Wed, 21 May 2003, Olivier Billard wrote:
>
> > Hi Giacomo !
> >
> > Thanks for answering
> > Unfortunately, when you "build clean" and "build webapp", the build
> > directory is deleted, no ?
>
> So what! You Ant script should take care of reinstalling everything
mentioned in
> my earlier mail.
>
> Giacomo
> >
> > --
> > Olivier
> >
> >
> > ----- Original Message -----
> > From: "Giacomo Pati" <giacomo@apache.org>
> > To: "Cocoon Users" <cocoon-users@xml.apache.org>; "Olivier Billard"
> > <obillard@jouve.fr>
> > Sent: Wednesday, May 21, 2003 3:57 PM
> > Subject: Re: How to keep own sitemap clean between CVS updates ?
> >
> >
> > > On Wed, 21 May 2003, Olivier Billard wrote:
> > >
> > > > Hi all !!
> > > >
> > > > I think the thread of my previous mail was not very attractive nor
very
> > > > clear...
> > > >
> > > > I'm trying to use the most recent Cocoon for my project, to follow
the
> > fixes
> > > > of the milestones versions.
> > > > But to keep my components configurations and to keep my project
sitemap
> > > > "clean" I would like to (until project production) keep it in a
> > project.xmap
> > > > file and reference it in sitemap.xmap, this file changing sometimes
> > after a
> > > > CVS update/build webapp.
> > > >
> > > > My question is : what is the most efficient way to do this ?
> > > > Or what is the best way to keep my own sitemap configuration
(components
> > > > configurations and pipelines) between two CVS update/build sequences
?
> > > >
> > > > 1 - Add <map:mount> element in a <map:pipeline> if possible
in the
> > > > sitemap.xmap
> > > > <map:pipelines>
> > > >     <map:pipeline>
> > > >         <map:mount check-reload="yes" src="project.xmap"
uri-prefix=""/>
> > > >     </map:pipeline>
> > > >  </map:pipelines>
> > > >
> > > > 2 - Some very wonderfull but very secret patch system created just
for
> > this
> > > > use.
> > > > 3 - anything else ?
> > >
> > > 0. build you cocoon with './build.sh'
> > > 1. keep your project sitemap named sitemap.xmap
> > > 2. deploy your xml/xslt/sitemap.xmap/js etc. into a directory at
> > >    [cocoon-2.1]/build/webapp/YOUR_PROJECT (this can be easily done by
> > >    Ant)
> > > 3. deploy your jars into [cocoon-2.1]/build/webapp/WEB-INF/lib (Ant as
> > well)
> > > 4. Use the XConfToolTask to manipulate the cocoon.xconf in
> > >    [cocoon-2.1]/build/webapp/WEB-INF/ (you guess it: Ant is your
friend)
> > > 5. start your cocoon with './cocoon.sh servlet-admin'
> > > 6. point your browser to http://localhost:8888/YOUR_PROJECT/
> > >
> > > Thats it.
> > >
> > > Giacomo
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> > > For additional commands, e-mail: cocoon-users-help@xml.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> > For additional commands, e-mail: cocoon-users-help@xml.apache.org
> >
> >
> >
> >
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org


Mime
View raw message