Re: [Babeldoc-devel] One configuration file for all babeldoc settings?

[Dejan K. <dej...@nb...>]

I am not sure about this... Why would one large xml configuration file would
be harder to manage than many small properties files or xml files (in case
of xml pipeline configuration). What about SQL configuration? In my opinion
it is even harder to manage then large xml file.

Anyway, having XMLConfigService would not prevent using LightConfigService.
So if user wants to use LightConfigService he could use it, just like he can
use SqlConfigService now (I guess he can, I haven't tried it!)

Dejan

----- Original Message -----
From: "Bruce McDonald" <br...@mc...>
To: "Dejan Krsmanovic" <dej...@nb...>
Cc: "Babeldoc Developers List" <bab...@li...>
Sent: Tuesday, February 25, 2003 4:45 PM
Subject: Re: [Babeldoc-devel] One configuration file for all babeldoc
settings?


> Having one configuration file for babeldoc is not going to happen for the
> simple reason is that it couples non-coupled code.  As for ant having one
> big configuration file - this is a real problem and lots of projects break
> apart the build.xmls.  There are lots of reasons why this is a problem -
> the most imporant one is that it becomes hard to manage.
>