> 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.
It is very unlikely that any real mmbase app will not have it's own
WEB-INF/config directory. it's not called config by hazard :)
Having the resources and dtd's in the src tree was a bad idea in the
first place. worse is if like now we have both resources configs all
over the place for no apparent reason (other than making it difficult
to find dtd's and validate xml's)
_______________________________________________
Developers mailing list
[EMAIL PROTECTED]
http://lists.mmbase.org/mailman/listinfo/developers
