Re: Log4CXX Maintenance
On 07.08.2013 06:57, Christian Grobmeier wrote: [...] If there are such people, I would support moving the project to the Apache Incubator (incubator.apache.org) and help folks to learn about our procedures. snip (Hi) So it means that you wasn't convince by the people who reply to your announce (or they wasn't enough)? .. and what about the alternate proposition to enable git mirror (ok - some forks are already here and denotes activities) with log4j's mentor looking on the patches ? BTW, having the project under Incubator seems a better way for me. Regards Florian
Re: log4cxx - reaching out for interested developers
Le Thu, 18 Apr 2013 13:04:25 +0200, Christian Grobmeier grobme...@gmail.com wrote : [...] Basically there are many people who keep an eye on the project, discuss, commit a few things but keep their level of activity pretty low. This works too, as long as the person sticks with the project. snip Hi All, As a user of this great library since almost 7 years (with some discontinuities) , I'll be very happy to see it back online. The proposition of Christian to move them on Incubation stage makes sense, and seems even very appealing. Despite I didn't actively contributed till now, I would be very happy to offer some of my time for such task, following the quoted opinion here above. Of course, starting by simply providing patches would already be a first step for me - I just wanted to let you know that there are potential workpower, just waiting some activity on the lib to be 'activated'. Cheers Florian
Re: Best strategy to ensure a rolling when an application is launched
Curt Arnold wrote: logcxx::rolling::RollingFileAppender supports user-provided TriggeringPolicy's (which determines when a rollover should be attempted) and RollingPolicy's (which determine what file names to use). In this case, you could write your own TriggeringPolicy that triggers a rollover on application start up or when the application rolls over a date change or some other criteria. Great -- I'll try that. Thanks a lot.
Best strategy to ensure a rolling when an application is launched
Hello, I'm using log4cxx with a standard application (not supposed to be runned continuously), but I want to have two logs, one per day (in order to check potential problems returned by the 'users', i.e. probably not immediately) , and another per run (with retention of 5~10 runs), for debugging purpose. Unfortunately, both RollingFileAppender and DailyRollingFileAppender can't be used (at least directly), because the application is supposed to be running when it's time to roll. At your opinion, what is the best way for me to 'force' a test of the rolling policy when the application is runned ? Should I create my own appender, or there is something that I've missed ? regards fs (and sorry for my poor engl).
