Andr? van Toly <[EMAIL PROTECTED]> wrote:> >Indeed. But now it is in core too. Where it actually was missing was in the >xmlimporter application, I think.
OK. I'll put it there. And this means it should not be in de /WEB-INF/config/modules directory but in the config/modules directory of the application? Because by default it is inactive?
Yes, the install target of the application will put it there (if you use it). Also in the package's zip it will be in WEB-INF/config (so unpackging the zip will install the app).
I thought so.
By default it can be set active in the application, because the application makes not sense without it.
If you wanted it inactive, you should not have installed it it the first place, I figure..
OK. I get it. But what's the policy? For instance: In 1.7 rc2 modules/communityprc.xml is set to active although the application itself is not installed (autodeploy=false) and generated a warning in the log cause it is unable to find it's builders, like message.
2004-03-12 13:25:47,022 WARN applications.community.modules.CommunityPrc - Community module could not be activated because message builder missing or could not be activated
And there are even more inactive configuration files in the config/modules directory that as far as i know don't have any applications related to them. Currently in 1.7rc2:
communityprc.xml active config.xml active jdbc.xml active linkchecker.xml inactive mmadmin.xml active mmbaseroot.xml active mmflash.xml inactive mmusers.xml inactive rmmci.xml inactive sendmail.xml inactive stats.xml inactive upload.xml inactive xslconvert.xml inactive
---Andr� --
------------------------------------------------------------------>><<-- Andr� van Toly http://www.toly.nl 06-27233562
