Re: [Developers] VOTE: Optimization STEP 9: adapting build.xml forconfiguration

2004-12-02 Thread Kees Jongenburger
They are (or should be) all available on http://www.mmbase.org/dtd. Otherwise a find . -name *.dtd in the src dir would quickly find it. neither are good options http://www.mmbase.org/dtd don't always match you mmbase version and if you USE mmbase your don't have the source available

Re: [Developers] VOTE: Optimization STEP 9: adapting build.xml forconfiguration

2004-12-02 Thread Michiel Meeuwissen
Kees Jongenburger wrote: They are (or should be) all available on http://www.mmbase.org/dtd. Otherwise a find . -name *.dtd in the src dir would quickly find it. neither are good options http://www.mmbase.org/dtd don't always match you mmbase version It should, because the version of the

RE: [Developers] VOTE: Optimization STEP 9: adapting build.xml forconfiguration

2004-11-30 Thread Nico Klasensn
[X] -1 (NO), because : 1 adding only this to the target means duplicating config files in the distribution, isn't it? And why do we then still need the first copy-tag? 2 Adding all config files to the main jar would mean that MMBase will always fallback to default config files when they are

Re: [Developers] VOTE: Optimization STEP 9: adapting build.xml forconfiguration

2004-11-30 Thread Pierre van Rooden
Nico Klasensn wrote: 1 adding only this to the target means duplicating config files in the distribution, isn't it? Yes, unless we exclude the config dir in the ditribution, which is likely not very helpful. And why do we then still need the first copy-tag? The first copy tag copies resources