Good to hear.
I am very interested in using log4cpp on a project but I have certain questions with regard to a roadmap of when certain features might be available.
Can someone point me to something like this, maybe a todo list? This will really help me in understanding the current status and future release path. Also, I would be interested to help with developing certain components and having a todo/roadmap will help me identify if and how I can contribute.
thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the CVS repo you can find a small TODO list, I made a while ago. Admittedly it is not very complete.
As for a roadmap: my plans are to have a release we confidently can call stable (i.e. no memory leaks or crashed on ALL used platforms) in the short term (the next few weeks). This version should be OK for production systems. It will have the same functionality as current CVS HEAD, i.e. pretty basic, but usable.
I currently have NO roadmap for new functionality: I really like to see support for configurators or multithreads NDC's, but new releases all depend on who contributes what and when.
If you like to contribute, you're very welcome of course. Basically I suggest you scratch your own itches, but you could also have look at log4j for inspiration. Some things I personally like to see are:
* configurators (Cedric is already working on a basic one)
* a PatternLayout class
* thread local NDCs and multithread readiness of all logging
Regards,
Bastiaan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As far as I know noone has started work on a PatternLayout class yet, but you could ask on the development mailing list.
If you like to do some work in this area you're very welcome.
Bastiaan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You guys are great, thanks for moving this to c++
I had a look at the log4j documentation on runtime configuration:
PropertyConfigurator.configure(conf_file)
I cannot find a similar class in the log4cpp lib.
How do we support runtime configuration in the log4cpp lib?
Thanks
log4cpp status is still Alpha.
The runtime configuration system is not available yet. Be patient, we're working on it :-)
C.
Good to hear.
I am very interested in using log4cpp on a project but I have certain questions with regard to a roadmap of when certain features might be available.
Can someone point me to something like this, maybe a todo list? This will really help me in understanding the current status and future release path. Also, I would be interested to help with developing certain components and having a todo/roadmap will help me identify if and how I can contribute.
thanks
Bastiaan will explain this in details when he comes back from holiday.
You can check the TODO file in latest CVS tree.
I've been working on the configurator Pattern but I didn't have time to integrate it yet.
C.
Thanks to everyone working on this project! log4cpp is exactly what our highly multithreaded and distributed application needs!
How far along is the pattern configurator? Any estimate on when it might be available?
Thanks.
- David
Hi Tom,
In the CVS repo you can find a small TODO list, I made a while ago. Admittedly it is not very complete.
As for a roadmap: my plans are to have a release we confidently can call stable (i.e. no memory leaks or crashed on ALL used platforms) in the short term (the next few weeks). This version should be OK for production systems. It will have the same functionality as current CVS HEAD, i.e. pretty basic, but usable.
I currently have NO roadmap for new functionality: I really like to see support for configurators or multithreads NDC's, but new releases all depend on who contributes what and when.
If you like to contribute, you're very welcome of course. Basically I suggest you scratch your own itches, but you could also have look at log4j for inspiration. Some things I personally like to see are:
* configurators (Cedric is already working on a basic one)
* a PatternLayout class
* thread local NDCs and multithread readiness of all logging
Regards,
Bastiaan
As far as I know noone has started work on a PatternLayout class yet, but you could ask on the development mailing list.
If you like to do some work in this area you're very welcome.
Bastiaan