I would add one simple point - in my experience of configuring Cocoon, there are only a couple of details from the build.properties that I actually need - particularly the exclude.webapp, etc. I would leave most of build.properties in that file, but move the first few entries into a configure.properties (along with all of the blocks.properties stuff). That way the user only has to edit one file to configure Cocoon. This would be a good thing.
Regards, Upayavira
Timothy Larson wrote:
Ok, could you see the example production install configuration as the template for a binary distribution?
Whether or not there is a binary distribution, I agree that we should have the post-build script that you mention. Download the binary distribution or do a custom build, then use separate config files to pull together various web-apps.
Something conceptually like (did not think about syntax yet): ./configure webapp with-config-file=custom-development-webapp.properties ./configure webapp with-config-file=custom-production-webapp.properties
Does this last part match what you are suggesting? If we put this on a (probably separate) wiki page then the developers can also contribute. I understand not all of them are subscribed to the users list.
--Tim Larson
--- Ralph Goers <[EMAIL PROTECTED]> wrote:
I don't really want to edit your page because I disagree with the premise (i.e. requiring "customers" to build from source). Cocoon should have a single build that is its binary distribution. It should have a post-build script to create a web-app that meets the users needs.
Ralph
__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
