Re: [FEEDBACK NEEDED] Cocoon build-installation wishlist
On Monday 29 April 2002 05:26, you wrote: We are in the process of touching the build system to make it easier for users to build and deploy Cocoon. Great! What do you think of them, and what would you like to see in the Cocoon build-installation? [X] creation of minimal Cocoon WAR I feel Peter's pain. I too have so far stayed away from updating from Cocoon1. All I want to do is render existing (static) XML files with existing (static) XSL(T) stylesheets. I can even live with associating stylesheets based on URI's, but the default build of Cocoon2 comes with so much stuff (which is certainly useful in other contexts) that it is a real pain to set up a minimalist environment for simple XSLT. There shouldn't be any need for outside projects such as Chello. Oh and BTW, throwing RTFS's (Read the fucking sitemap) at people does not IMHO facilitate the proliferation of a technology with a substantial learning curve. Thanks for all the constructive advise, Thorsten - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [FEEDBACK NEEDED] Cocoon build-installation wishlist
On Monday, April 29, 2002, Nicola Ken Barozzi wrote: We are in the process of touching the build system to make it easier for users to build and deploy Cocoon. This is exciting news! The interactive, installwar and installscratchpadwar targets have been a first try in that direction. What do you think of them, and what would you like to see in the Cocoon build-installation? + I don't think the default build target is newbie-friendly. I wish typing ./build.sh would bring up projecthelp options. Perhaps there needs to be separate user and developer/advanced build.xml files. + Newbies trip up all the time about how and when to to build clean. Perhaps it needs to be recommended -- interactively -- as an option before a build for a selected target begins. + I wish projecthelp options were more verbose about the real world purpose of the targets. Why is there no information at all about subtargets? IMHO are just too many concerns mixed into the single build file. + I think most users miss the fact interactive builds exist. Even if you notice the interactive build files in the tools directory, it's not obvious how to use them. + I'm wonder exactly how many users actually build their Cocoon WARS, as opposed to those who simply download the binary version. Do you have access to download statistics? Please comment and add at will; detailed descriptions of use cases are very welcome. [ ] default interactive build This would help. Make sure there is some degree of error recovery, if possible with ant. For example, some interactive builds fail if you input the wrong data. This is a little frustrating. [ ] creation of minimal Cocoon WAR This would be wonderful, but I think opinions will vary as to what is truly minimal. Perhaps even a minimal build could include some additional degree of interaction? [ ] creation of personalized build - choose optional components Great, assuming it includes sitemap and cocoon.xconf synchronization. [ ] GUI installation (how?) Not a high priority for me. Seems to me ant should be sufficient, along with a little more echo-based feedback as the build process unfolds. [ ] Add your wish + I'm not sure this is the responsibility of a build tool, but there's always a concern, when I'm learning a new software, about when to apply patches, test new scratchpad features, etc. For example, let's say I have my finely tuned Cocoon project, working perfectly, but I'd *really* like to try some new thing announced on the list. I'd like to add this new functionality to my setup, but be able to back out of it, if possible. In other words, deconstruct a build. Perhaps this is a best practice tip about working effectively with cvs, not the domain of a build tool. + Is it even practical to think you could generate a head or release target out of a one build session? + Different configuration files, based on the goal of the build target, e.g. development vs. production, recommended memory/cache settings, based on deployment environment, etc. I would love to volunteer for usability testing, down the road, if you need some feedback! Thanks a lot. Diana - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [FEEDBACK NEEDED] Cocoon build-installation wishlist
Hi! We are in the process of touching the build system to make it easier for users to build and deploy Cocoon. The interactive, installwar and installscratchpadwar targets have been a first try in that direction. What do you think of them, and what would you like to see in the Cocoon build-installation? Please comment and add at will; detailed descriptions of use cases are very welcome. [ ] default interactive build [ ] creation of minimal Cocoon WAR [ ] creation of personalized build - choose optional components [ ] GUI installation (how?) Maybe with help of InstallAnywhere? Is it possible to do it like in Tomcat? [ ] Add your wish [ ] Documentation and/or samples only Thank you :-) You're welcome ;) Konstantin -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.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/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [FEEDBACK NEEDED] Cocoon build-installation wishlist
At 14:13 29/04/2002 +0400, you wrote: Hi! We are in the process of touching the build system to make it easier for users to build and deploy Cocoon. The interactive, installwar and installscratchpadwar targets have been a first try in that direction. What do you think of them, and what would you like to see in the Cocoon build-installation? Please comment and add at will; detailed descriptions of use cases are very welcome. [ ] default interactive build [ ] creation of minimal Cocoon WAR [ ] creation of personalized build - choose optional components [ ] GUI installation (how?) Maybe with help of InstallAnywhere? Is it possible to do it like in Tomcat? [ ] Add your wish [ ] Documentation and/or samples only Maybe I'm moving on thin ice here considering the move to blocks. [ ] A minimal source distribution + doc on how to implement your own components and build the webapp This will allow people to create and distribute their own webapps. I think many people would love to send a WAR file with their developed webapp to a customer for a review. Bert - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Several C2.war in the same servlet container (was : RE: [FEEDBACK NEEDED] Cocoon build-installation wishlist)
This will allow people to create and distribute their own webapps. I think many people would love to send a WAR file with their developed webapp to a customer for a review. Bert I've tryed this to show benefits of several implementation of a C2 webapp... but i found that in my configuration (tomcat 4.0.1, C2.0.2 and C2.0.3Dev), i've noticed that having several war containing cocoon is NOT a good idea (many exception caught at runtime, and some samples stopped working, while all worked perfectly when only 1 of the .war) Does this mean that, for now, you can't deliver a C2 webapp as a simple .war if the servlet container allready have a C2 webapp installed ? fabien. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [FEEDBACK NEEDED] Cocoon build-installation wishlist
I wish for a tree structured component checkoff display (like linux application/installation managers, or windows install) - that let's me select the components I will use in an installation. - that checks dependencies informs me - that lets me add something later without reinstalling everything - that tells me what I have already installed - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
