I don't know how applicable this is here, but . . . VIM has the ability both to initialize from a profile (configuration file) in a relatively fixed, standard place ($VIM/.vimrc, etc) and from a profile in one's current working directory. One can also execute (include) a profile from any other location from within either one. HTH, just a thought. Ron
-----Original Message----- From: Ceki G�lc� [mailto:[EMAIL PROTECTED] Sent: Saturday, March 29, 2003 3:08 PM To: Log4J Users List Subject: Re: Inherited Logger Config? At 03:02 PM 3/29/2003 -0500, you wrote: >Yes you are right Ceki, and I do have great respect for Yoav's >contribution efforts. I am also always for anyones free expression of opinion. Pardon my babbling but when I say freedom of opinion, I do not only mean the liberty to criticize a powerful political figure (e.g. head of state) and live to see the next morning. That sort of liberty can now a days be found in quite a few countries, (liberal democracies). What is really unique here at Apache is not only freedom of opinion but also the culture of debate that we have. One can say almost anything without running the risk of being ostracized. Now, that's pretty special. ... >I just feared the overall reaction was to suggest the hierarchical logging >configuration was a bad idea, when in fact I believe it is a valid concept >to explore in discussion. I don't believe it to really be very complex a >concept. My goal was to clarify my opinion and defend my position. I >understand that it would not be something one would want to make the >"default behavior" in Log4J. Yoav's opinion on that particular issue is >quite valid and acceptable. > >However, exploring the development of a Hierarchical Configurator would be >of interest to some out there and could be done quite independent of the >Log4J projects basecode itself, thanks to the well separated Configurator >interface. Simply look at projects like Maven to see the benifit of >Hierarchical Configuration Inheritance. This is really where my idea >originated from. In Maven, the developer can designate build.properties >files in several clearly defined locations (user.home, maven.home, ...) to >isolate configuration information that is shared across many projects that >the developer would not want to be seen in the cvs (like cvs usernames and >site update configuration like ssh/scp executable locations). Things that >are really custom and unique to a particular build enviroment and developer. In log4j, we don't really have a concept of developer based configuration files. Configuration files are much more application based rather than developer based, which may well be a deficiency we have. One possible solution is to let log4j config files to optionally include parts of the configuration from other files. >Cheers, >Mark -- Ceki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
