RE: How to access configuration files and properties after packaging

2008-07-03 Thread Robin Rigby
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 -Do

Re: How to access configuration files and properties after packaging

2008-07-03 Thread Andy Stevens
2008/7/3 Robin Rigby <[EMAIL PROTECTED]>: > 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.pr

Re: How to access configuration files and properties after packaging

2008-07-03 Thread Johannes Hoechstaedter
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

RE: How to access configuration files and properties after packaging

2008-07-03 Thread Robin Rigby
-Original Message- From: Robin Rigby [mailto:[EMAIL PROTECTED] Sent: 03 July 2008 12:23 To: users@cocoon.apache.org Subject: RE: How to access configuration files and properties after packaging Here is one way that seems to work. Make a separate set of configuration for development and the

RE: How to access configuration files and properties after packaging

2008-07-03 Thread Robin Rigby
Hoechstaedter [mailto:[EMAIL PROTECTED] Sent: 03 July 2008 12:45 To: users@cocoon.apache.org Subject: Re: How to access configuration files and properties after packaging Robin Rigby schrieb: > Here is one way that seems to work. Make a separate set of configuration > for development and the defau

Re: How to access configuration files and properties after packaging

2008-07-03 Thread Johannes Hoechstaedter
ow to access configuration files and properties after packaging 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\prope

Re: How to access configuration files and properties after packaging

2008-07-03 Thread Johannes Hoechstaedter
Robin -Original Message- From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] Sent: 03 July 2008 12:45 To: users@cocoon.apache.org Subject: Re: How to access configuration files and properties after packaging Robin Rigby schrieb: Here is one way that seems to work. Make a

Re: How to access configuration files and properties after packaging

2008-07-03 Thread Barbara Slupik
: etc Robin -Original Message- From: Johannes Hoechstaedter [mailto:[EMAIL PROTECTED] Sent: 03 July 2008 12:45 To: users@cocoon.apache.org Subject: Re: How to access configuration files and properties after packaging Robin Rigby schrieb: Here is one way that seems to

Re: How to access configuration files and properties after packaging

2008-07-03 Thread Johannes Hoechstaedter
access configuration files and properties after packaging 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