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 from the src tree.
I prefer runtime crashing above runtime assuming. A seperate jar or only the very unlikely modified resources would have my +1.
We could filter certain resources, but which would these be? And how are we going to filter the right configs?
An alternate possibility is to move the 'core' config (core builders, stoarage ersoyrces, dtds, basic default configuration xmls) into the src tree, and instead of copying the config to the jar, copy the contents of org.mmbase.config to the config dir.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Some Drink at the Fountain of Knowledge. Others Just Gurgle."
_______________________________________________ Developers mailing list [EMAIL PROTECTED] http://lists.mmbase.org/mailman/listinfo/developers
