From: Stefan F. <ste...@we...> - 2010-07-18 17:35:09
|
Erik, sorry for the confusion. The explanation is below. I did a few changes on Config at the same time of your fix. Unfortunately the merge mechanism was totally confused by some other changes (import statements, white space) from your side, thus I had to integrate the fix manually. Could you please check that it still works. Two remarks: * Please replace the -Dlog4j= option with -Dlog4j.configuration= to set your user-defined log4j configuration file. Does not make much sense to use one system property to write it to another already defined by log4j. * Unfortunately I only tested mine with a copy of log4j.properties, but did not change anything the file content. The program worked before, but only by chance: I have used the default name for a log4j configuration file, thus even if log4j.configuration was not set, it fell back automatically to that file. Thanks, Stefan On Sunday 18 July 2010 19:07:23 Erik Vos wrote: > Stefan, > > Your fix didn't work yet, because logging was initialised (by creating a > logger in Config) before the relevant system property was set. I have > changed Config by deferring logger initialisation until just after the > system property is set, and now I'm fine. > > Erik. > > -----Original Message----- > From: Stefan Frey [mailto:ste...@we...] > Sent: Sunday 18 July 2010 00:38 > To: Development list for Rails: an 18xx game > Subject: Re: [Rails-devel] Added prototype configuration UI > > I have added a -Dlog4j option that can specify a file, which contains the > log4j settings. It can point to the same file as -Dconfigfile. > > > > --------------------------------------------------------------------------- >--- This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |