> Other log4j config files are all removed. That includes the log4j.properties under jdbc. The jdbc as a lib should log with the hosting application, should not have its separate log file.
On Mon, Oct 5, 2015 at 8:29 PM, Luke Han <[email protected]> wrote: > Hi Yang, > Could you please also check jdbc module's log4j setting? > It will always generated log file under "jdbc" folder when run UT > which will always bring exception when execute maven release (broken rat > rule). > > thanks. > > > > > Best Regards! > --------------------- > > Luke Han > > On Sun, Oct 4, 2015 at 10:11 PM, Li Yang <[email protected]> wrote: > > > Just fixed KYLIN-457 and deprecated the old (many) log4j.properties. > > > > - Under the common module, old log4j.properties is renamed to > > *kylin-log4j.properties*. DebugTomcat use it, log to console only. > > - Under the server module, old log4j.properties is renamed to > > *kylin-server-log4j.properties*. This is used by kylin server, log to > file > > system. > > - Other log4j config files are all removed. > > > > So no more confusions around which log4j.properties is being used. > > > > Cheers > > Yang > > >
