> turbine is not only the turbine.jar .. we use velocity, > commons-packages, ... > all this packages use different logging packages (log4j, > commons-logging, ...) > > so it will not be possible to have one single logging mechanism for all > of them ... > i think this is a problem which should be discussed on the general list
Yes, we are stuck with configuring many logging mechanisms now, and will continue to be. I thought the more immediate concern was logging WITHIN turbine and its associated services. For _that_ case I would like to see the avalon idiom and interfaces used, especially when we are already planning on using their lifecycle. It doesn't _matter_ what the actual logging mechanism is in such a case. I'm sure any of us with a reasonable complex application will be stuck configuring 3 or more anyway. Tangent: I'm all for sharing code, but what makes something in commons better than something in avalon-framework? Commons is pretty much unregulated, there is no reason to believe any of the commons projects are the best solution. Avalon-Framework has been through a number of revisions and has been fought over and refined for much longer than anything in commons. Lets make a decision that is technically best, and then work out the politics. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
