Re: local site setup
Hi, try the target clean-webapp on build, you will get a clean cocoon without samples. The other possibility is that you work in webapps/cocoon directory. You can try to work in a subdirectory that you mount in the main sitemap so that you don't lose all samples and docs (that are very valuable for the start). for example: webapps/cocoon/mytests and mount it in the main sitemap.xmap with: !-- pipeline mounting the test dir -- map:pipeline map:match pattern=mytests/** map:mount check-reload=yes src=mytests/ uri-prefix=mytests/ /map:match /map:pipeline have fun with cocoon ! Kim Peter Koellner wrote: hi! i'm sure this must be some dumb beginner's question, since nobody seems to have asked it until now. ok. now i have got this bright new xml-cocoon2 from cvs, built it, copied the war file to tomcat3.3's webapps directory, got the whole site running. so far, so good. what i don't quite understand at the moment is how am i supposed to remove the whole demo site and add my own content without intermingling with the cocoon cvs tree? i mean, do i have to work inside the cocoon directory, which obviously was generated from the war file? or even inside the cocoon source repository? can't be, or can it? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: local site setup
From: Kim Jelmoni [mailto:[EMAIL PROTECTED]] Hi, try the target clean-webapp on build, you will get a clean cocoon without samples. The other possibility is that you work in webapps/cocoon directory. You can try to work in a subdirectory that you mount in the main sitemap so that you don't lose all samples and docs (that are very valuable for the start). for example: webapps/cocoon/mytests You can simply copy the /samples/myapp to the /cocoon/myapp and start with it. and mount it in the main sitemap.xmap with: !-- pipeline mounting the test dir -- map:pipeline map:match pattern=mytests/** map:mount check-reload=yes src=mytests/ uri-prefix=mytests/ /map:match /map:pipeline It's not required. Every sub-directory of the context root (/cocoon) is auto-mounted from the root sitemap. Konstantin have fun with cocoon ! Kim Peter Koellner wrote: hi! i'm sure this must be some dumb beginner's question, since nobody seems to have asked it until now. ok. now i have got this bright new xml-cocoon2 from cvs, built it, copied the war file to tomcat3.3's webapps directory, got the whole site running. so far, so good. what i don't quite understand at the moment is how am i supposed to remove the whole demo site and add my own content without intermingling with the cocoon cvs tree? i mean, do i have to work inside the cocoon directory, which obviously was generated from the war file? or even inside the cocoon source repository? can't be, or can it? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: local site setup
Hi Peter - Not a dumb question at all. In fact, until recently, you had to add your own build targets to build a clean example-less distribution. But now you can do: build.bat clean-webapp or build.sh clean-webapp. This gives you a clean war file, without any samples, that you can copy to your servlet container. Once you have a running app, then I suggest that when you rebuild Cocoon from the CVS sources, you copy the libs only from the build/cocoon/webapp/WEB-INF/lib directory. That way, you get the latest code but you don't have to mess up your sitemap.xmap and cocoon.xconf. That is, unless there are changes to those files in CVS. It is also a good idea to do your own work in a subdirectory of the main cocoon installation and have your own sub-sitemap. That way, all your stuff won't get stomped on if you happen to update the main sitemap. Good luck, Lajos Peter Koellner wrote: hi! i'm sure this must be some dumb beginner's question, since nobody seems to have asked it until now. ok. now i have got this bright new xml-cocoon2 from cvs, built it, copied the war file to tomcat3.3's webapps directory, got the whole site running. so far, so good. what i don't quite understand at the moment is how am i supposed to remove the whole demo site and add my own content without intermingling with the cocoon cvs tree? i mean, do i have to work inside the cocoon directory, which obviously was generated from the war file? or even inside the cocoon source repository? can't be, or can it? -- galatea.com Cocoon training, consulting support - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
