Robin Rigby schrieb:
Here is one way that seems to work. Make a separate set of configuration
for development and the default for production.
\src\main\resources\META-INF\cocoon\properties\config.properties
\src\main\resources\META-INF\cocoon\dev\properties\config.properties
and run during development with
mvn -Dorg.apache.cocoon.mode=dev jetty:run
It is documented somewhere _if_ you can find it. I suppose the same would
work in Tomcat, ect
Thank you for your answer Robin, but your configuration files are still
packaged in in the jar file, or? Thats what I want to pretend.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
