19 Mar
2010
19 Mar
'10
7:15 p.m.
On Fri, Mar 19, 2010 at 7:03 PM, Vincent Massol <vincent(a)massol.net> wrote:
for UC5
1/ We put a minimal list of plugins in core code, we don't put config
files in the WAR, we add a plugin to XE in the next release, the user
will have to update his config file
2/ We keep the default config for XE in the WAR, we add a plugin in
the next XE release, the user doesn't have anything to do (if we
encourage to only override some settings and not all)
I agree your solution is cleaner but imho it's not the most convenient
for admins. Also, I think the situation would be different if XE was
the platform, in this case we could put XE plugin list in the code.
Thanks,
JV.
It'd be perfect but some values aren't in the code, and some shouldn't
be imho, the first example I can think of is the list of plugins.
Yes, for values that don't have default in the code, I think we should move the in
the code. Actually that's:
UC5: Make XWiki work without configuration files.
Solution for UC5:
* Put default values in the code so that XWiki works if there's no xwiki.cfg,
xwiki.properties or hibernate.cfg.xml files. We would default to HSQLDB by default.