Re: Yet another logging facade

2017-04-07 Thread Ralph Goers
See http://stackoverflow.com/questions/41633278/can-we-use-all-features-of-log4j2-if-we-use-it-along-with-slf4j-api/41635246#41635246 . Note that item 10 on this

Re: Yet another logging facade

2017-04-07 Thread Ralph Goers
I just took a look at the list. I don’t see the response that points to bugzilla. In your comment you mentioned that Log4j provides an api but you didn’t list the reasons why it is better. Remko posted a stack overflow post that has 10 reasons why it is better. But more importantly, users

Re: Yet another logging facade

2017-04-07 Thread Matt Sicker
I got a response on the mailing list. There's a public bugzilla we can comment on apparently which is linked in the PDF. On 6 April 2017 at 20:02, Matt Sicker wrote: > I'm not sure where they develop the standards, but there's an osgi-dev > mailing list (where I found this

Re: Yet another logging facade

2017-04-06 Thread Matt Sicker
I'm not sure where they develop the standards, but there's an osgi-dev mailing list (where I found this posted today): https://www.osgi.org/community/mail-lists/ I don't see Apache on this list despite being the foundation behind most of the open source OSGi projects out there:

Re: Yet another logging facade

2017-04-06 Thread Gary Gregory
A quick review of the document appears to have SLF4J as a requirement. Shame about that. Gary On Thu, Apr 6, 2017 at 5:34 PM, Ralph Goers wrote: > Where does one comment on these? > > The problem is that they mention Java 8 support, but SLF4J doesn’t take >

Re: Yet another logging facade

2017-04-06 Thread Ralph Goers
Where does one comment on these? The problem is that they mention Java 8 support, but SLF4J doesn’t take advantage of any Java 8 features yet. No support for Lamda’s. From what I am seeing the next release will support running in Java 9 and will leverage StackWalker and support Java modules

Re: Yet another logging facade

2017-04-06 Thread Remko Popma
Good find. I noticed that the document points to Apache Sling and says "uses the most common parts today used for logging: SLF4J for clients and logback for processing." Seems like Sling decided that in 2013 and never looked back. Which is fine, but I believe Log4j2 has changed the landscape