Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate with Common Logging #321

Closed
davidshen84 opened this issue Nov 16, 2017 · 2 comments
Closed

Integrate with Common Logging #321

davidshen84 opened this issue Nov 16, 2017 · 2 comments

Comments

@davidshen84
Copy link

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.

@ghost
Copy link

ghost commented Nov 22, 2017

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.

@jonorossi
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants