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 but Ceki hasn’t mentioned if he is going to add to the API to support things users have been asking for.
I’d hate to see them base their standard on what was then the current release of SLF4J and then for it to be enhanced and they are stuck with a limited API. I wonder how much input, if any, Ceki had in this. As a side note, he also changed the binding mechanism and I am not sure if it is backward compatible, soI have a feeling log4j-slf4j-impl will need changes to support that version. Ralph > On Apr 6, 2017, at 4:00 PM, Remko Popma <remko.po...@gmail.com> wrote: > > 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 the last > 4 years. > > Sent from my iPhone > > On Apr 7, 2017, at 6:08, Matt Sicker <boa...@gmail.com > <mailto:boa...@gmail.com>> wrote: > >> OSGi is looking at updating their logging API: >> >> https://github.com/osgi/design/blob/master/rfcs/rfc0219/rfc-0219-LogService-Update.pdf >> >> <https://github.com/osgi/design/blob/master/rfcs/rfc0219/rfc-0219-LogService-Update.pdf> >> >> We might want to provide feedback. >> >> -- >> Matt Sicker <boa...@gmail.com <mailto:boa...@gmail.com>>
