On 17/06/2008, at 5:59 PM, Olivier Lamy wrote:
I have seen an empty mdo file in continuum-configuration ;-).
IMHO we can use it.
Is modello still a good choice, or is something more basic a better
option?
My first idea was to read the file in :
${user.home}/.continuum/continuum-configuration.xml.
You certainly have to make sure that it's not hardwired into the home
directory. It's a good default if you drop in a webapp, but it needs
to be changable, and in the Jetty distribution I think one under conf/
makes more sense so it can stay with the rest of the configuration.
We have a lot of flexibility in archiva like this, but it's also too
complex. I would avoid merging the two files, for example.
But to ensure backward comp, file from store if exists must win.
I would say if it's in the store, migrate it to the other
configuration and then remove it. The new file would always win.
I still like commons-configuration as a way to source the information,
especially since you can pull values from JNDI and system properties
that makes it straight forward to overrides some configuration.
- Brett
WDYT ?
--
Olivier
2008/6/17 Brett Porter <[EMAIL PROTECTED]>:
Cool. What technology will you use for the configuration?
On 17/06/2008, at 8:13 AM, Olivier Lamy wrote:
Hi,
If no objections, I can start to work on CONTINUUM-1252 because I
need
it to fix CONTINUUM-1489.
--
Olivier
2008/6/13 Emmanuel Venisse <[EMAIL PROTECTED]>:
I'm working on the build manager actually, but in few days, I'll
migrate
to
a Spring mail sender [1], at the same time, I'd like to work on the
possibility to override the template without to modify the webapp
content.
Maybe I'll work on CONTINUUM-1252 too
[1]
http://springtips.blogspot.com/2008/06/send-e-mail-using-spring-and-javamail.html
On Fri, Jun 13, 2008 at 5:13 PM, Wendy Smoak <[EMAIL PROTECTED]>
wrote:
On Fri, Jun 13, 2008 at 7:51 AM, Martin van den Bemt <[EMAIL PROTECTED]
>
wrote:
I am not particularly fond of having another config file that
we need
to
change or maintain in an
installation (besides the complexity for a lot of people
finding the
home
directory of the system
user in windows). Why not do it correctly right away and add
it to the
configuration page ? (didn't
check the data model yet, so I don't hope it needs db changes for
that).
We are planning to move the general configuration out to a text
file
so that it can be pre-configured (before you ever start the
app.) [1]
The requirement to visit that web page for each new installation
makes it difficult to automate server provisioning.
I don't think that really affects whether to put the mail notifier
config on that page, just where the data will be stored (in
continuum.xml and/or in the database.)
[1] http://jira.codehaus.org/browse/CONTINUUM-1252
--
Wendy
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
