Hi David, thank you. I can only apologise for not engaging earlier. I, and I think others, didn't appreciate the impact of the changes until recently.
Regards, Graham. On 1 February 2012 10:46, Guillaume Nodet <[email protected]> wrote: > Can't we simply do something in aries until that would be shared by > all aries modules (since they kinda all depend on it already) ? > A very small api that could be configured to either use slf4j, jul or > osgi logging ? Using optional imports, it should limit to what's > available and default to a good one, falling back to jul if nothing > else. > > On Wed, Feb 1, 2012 at 11:26, David Bosschaert > <[email protected]> wrote: >> Hi all, >> >> On 1 February 2012 09:58, Graham Charters <[email protected]> wrote: >>> Hi David, >>> >>> Prior to these changes, Apache Aries had the ability to filter logging >>> per class, and this was consistent across all Aries modules. >> >> Well apparently not because the Aries JMX component used the >> LogService already... >> >>> I don't >>> think we should be doing piecemeal infrastructure dependency changes >>> like these without a proper consideration. >> >> Well, you can see at the beginning of this thread (Jan 16) that I'm >> asking for opinions re removing to the LogService and that the >> responses where positive... >> >>> Although nobody really wants to have a logging conversation, I don't >>> think we can avoid one, and until then, I think we need to go back to >>> the consistent approach that, until now, Aries consumers seemed happy >>> with. >> >> ... sigh ... ok we'll have a logging discussion and I'll revert those >> changes for the moment. >> >> @David J: we can explore the capabilities of the log service in that >> discussion. >> >> Best regards, >> >> David > > > > -- > ------------------------ > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > FuseSource, Integration everywhere > http://fusesource.com
