Re: minimalist
Any idea when this reworking will be done ? (days, weeks, months, or years ? :) Is it just a fixing/cleaning up of the build system or is he actually upgrading it to some new ideas (which? ) many thanks for the replies already btw. :) On Wednesday 19 February 2003 14:32, Geoff Howard wrote: Well, you may want to wait a little to see what Stefano comes up with in reworking the build process - it may make things easier. I've seen pages on the web on creating a minimal cocoon 2.0 setup (only the neccecary jar files to run, a sitemap only specifying what the app you're building needs, absolutely no cocoon samples etc. ) but haven't found one describing how to do this for the cvs development version, cause I have to put this thing with jars and all under cvs I'd really like to know how tho :) what especially interests me is what is the minimal list of jar files needed, I've tried removing everything that's originally under /optional, but then things go wrong quite a bit. Also I wonder what's the best way to build cocoon with as little samples and sample related files as possible ? Any help 'd be greatly appreciated. Jeroen Cranedonk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: minimalist
It's a total reworking of the build process that can probably be expected to take days or weeks, not months or years. Since we originally talked the core build is working - it now completely avoids all samples out of the box (and figuring the samples out is not done yet). As I remember your desire was to build a minimal build that you could add your sitemap and setup to, so you may have what you need already. Do a current cvs checkout of 2.1dev, or get a very recent snapshot. Geoff At 11:26 AM 2/25/2003, you wrote: Any idea when this reworking will be done ? (days, weeks, months, or years ? :) Is it just a fixing/cleaning up of the build system or is he actually upgrading it to some new ideas (which? ) many thanks for the replies already btw. :) On Wednesday 19 February 2003 14:32, Geoff Howard wrote: Well, you may want to wait a little to see what Stefano comes up with in reworking the build process - it may make things easier. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
minimalist
I've seen pages on the web on creating a minimal cocoon 2.0 setup (only the neccecary jar files to run, a sitemap only specifying what the app you're building needs, absolutely no cocoon samples etc. ) but haven't found one describing how to do this for the cvs development version, cause I have to put this thing with jars and all under cvs I'd really like to know how tho :) what especially interests me is what is the minimal list of jar files needed, I've tried removing everything that's originally under /optional, but then things go wrong quite a bit. Also I wonder what's the best way to build cocoon with as little samples and sample related files as possible ? Any help 'd be greatly appreciated. Jeroen Cranedonk - 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: minimalist
Well, you may want to wait a little to see what Stefano comes up with in reworking the build process - it may make things easier. Also, do a build -projecthelp to see if there is a built in target that does this out of the box. I think there was at some point, but don't know if it's kept up with the most recent changes. I haven't tried this in a while with 2.1dev, but the basic roadmap would be to edit properties.xml to comment out as many blocks as desired. There are also some build properties to exclude things like javadocs, docs, and samples though you'll have to dig through build.xml to find them and experiment to see if they work as advertised. I believe there will also be the following caveats: 1) Not everything is refactored into blocks yet, so you'll need to also remove unwanted stuff from lib/optional (remember to also edit jars.xml to remove references to anything you remove from optional). It sounds like you did this part - can you be more specific about what went wrong? 2) There are some blocks that are still required (this should get fixed) so you will have to add them back in even if you don't need them. 3) There are some blocks that bundle in things you may want to get rid of. For example, if you need the database components you need to include the database block, but that also gets you the hsql component (although excluding samples may exclude it as well) which you probably don't want. You'd then have to remove that by hand (by editing cocoon.xconf, and web.xml) 4) There will be other tricks along the way - this is an area that is still being worked out. If you start working on this, report back specifics as you go and I or others can help move things along. Geoff Howard At 04:26 AM 2/19/2003, you wrote: I've seen pages on the web on creating a minimal cocoon 2.0 setup (only the neccecary jar files to run, a sitemap only specifying what the app you're building needs, absolutely no cocoon samples etc. ) but haven't found one describing how to do this for the cvs development version, cause I have to put this thing with jars and all under cvs I'd really like to know how tho :) what especially interests me is what is the minimal list of jar files needed, I've tried removing everything that's originally under /optional, but then things go wrong quite a bit. Also I wonder what's the best way to build cocoon with as little samples and sample related files as possible ? Any help 'd be greatly appreciated. Jeroen Cranedonk - 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: minimalist
Here's the skeleton of a document I'm writing about a procedure that worked for me. I tried to pass all of this information via the build scripts, but all I got back was the prompt (and no build). I ran everything by using the Ant that comes with the CVS download of Cocoon. Since I currently only have a Win/2000 machine to work on, the notes have a Windows flavor. Do the normal DOS-UNIX translation to get the UNIX version. If you want to reduce the size of Cocoon, you'll want to avoid adding -Dinclude.scratchpad.libs=yes as well as adding the optional libs I put in on steps 2 and 3. My purpose in putting this together was to build a sandbox that I could use to experiment with various Cocoon ideas and prototype applications. Hopefully I'll get this entire thing written up, as well as the appropriate 2.04 documentation sometime soon. HTH /mde/ just my two cents . . . . __ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com ** Cocoon Sandbox 1. Obtain latest version via CVS 2. Put optional jars in lib/optional a) commons-logging-1.0.jar (for POI) from http://jakarta.apache.org/commons/logging.html b) mail.jar (for mail client) from http://sun.java.com/products/javamail/ c) phpsrvlt.jar (for php source) from http://www.php.net 3. Put local jars in lib/local a) activation.jar (for JavaBeans) from http://java.sun.com/products/javabeans/glasgow/jaf.html b) jta.jar (for distributed transactions) from http://java.sun.com/products/jta/ c) xindice.jar (for xml database) from http://xml.apache.org/xindice/ 4. Edit lib/jars.xml to reference new jars in the lib/optional directory 5. Edit properties.xml to turn off debugging and turn on optimization (optional). 6. Make sure evironment variables are cleared. a) SET CLASSPATH= b) SET ANT_HOME= 7. Set ANT_HOME to Cocoon's ant a) SET ANT_HOME=tools 8. Build Cocoon without samples, javadocs, and documentation. tools\bin\ant -Dcocoon.webapp.samples.include=false \ -Dcocoon.webapp.documentation.include=false \ -Dcocoon.webapp.javadocs.include=false \ -Dinclude.webapp.libs=yes \ -Dinclude.scratchpad.libs=yes \ -Dinstall.war=%TOMCAT_HOME%\webapps \ webapp 9. Rename the resulting cocoon.war to capps.war (or another name) 10. Drop capps.war into %TOMCAT_HOME%\webapps 11. Delete all empty directories (optional) 12. Modify sitemap.xmap to create a reasonable welcome file 13. Change logging levels in logkit.xmap (optional) 14. Change application description in web.xml (optional) - 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]
