You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Common Logging looks like a sane project. Would people like the idea that Castle integrate this logging interface. This should remove the necessity to implement and maintain a range of logging frameworks by Castle project.
Both Castle and Common Logging are using Apache 2.0 license.
The text was updated successfully, but these errors were encountered:
Not convinced. If anything I want reduce vendor lock-in when it comes to logging libraries or abstractions. These things are so trivial to implement if done right, why oh why do we need another layer of abstraction around this? What if a user only wants feature X from log4net but Common Logging does not implement feature X because it is different from the SeriLog driver? This is really stuff that should be in the users hands directly.
I agree with @Fir3pho3nixx, Common.Logging is quite a complicated project and if we wanted to keep an abstraction I'd prefer to just keep the one we've got rather than move to yet another as it doesn't simplify build/test time dependencies.
Check out castleproject/Windsor#339 where we are currently talking on this topic. I'll close this in favour of the discussion in the Windsor repo.
Common Logging looks like a sane project. Would people like the idea that Castle integrate this logging interface. This should remove the necessity to implement and maintain a range of logging frameworks by Castle project.
Both Castle and Common Logging are using Apache 2.0 license.
The text was updated successfully, but these errors were encountered: