[slf4j-user] Slf4j 2.0 future

[Ceki]

Hi Joakim,

Indeed, I am aware that Jetty has been supporting/using slf4j since 
early on. Thank you!

I was not aware that Jetty and Eclipse IDE was using slf4j 2.0.0-alpha.

As you are probably aware, slf4j 2.0 introduces a fluent logging API 
which is quite an enhancement with respect to the traditional logging 
API. Are you using the fluent API at all?

Thank you for your offer to help. It is much appreciated.

Do you see any issues that are blocking on your end? With slf4j's JPMS 
support perhaps? Maybe OSGi?

More concretely, in SLF4J-457, see [1], the MANIFEST.MF file was 
modified [2] by adding a "Require-Capability:" statement, see [2]. How 
safe is this addition in OSGi environments? In non-OSGi environments?

Best regards,


[1] https://jira.qos.ch/browse/SLF4J-457
[2] https://github.com/qos-ch/slf4j/commit/4a1d5194fe

--
Ceki




On 10.06.2021 14:41, Joakim Erdfelt wrote:
> Hey Ceki,
> 
> Hi from the Eclipse Jetty project.
> We've been supporting slf4j in Eclipse Jetty since Jetty 5.x (and slf4j 
> 1.1.0)
> 
> Recently (in the past 2 years), we moved to slf4j 2.0 because it was our 
> favorite logging facade and had support for JPMS. (proper JPMS support 
> was the huge deciding factor)
> We did this with our Jetty 10.x series (and Jetty 11.x series), which 
> have had 4 stable releases each so far.
> We have a JPMS web server with a JPMS based logging facade.
> 
> We've had great success, and even wrote our own minimal implementation 
> of slf4j-api 2.0 that we use for our minimal deployments (even 
> supporting JPMS).
> https://github.com/eclipse/jetty.project/tree/jetty-10.0.x/jetty-slf4j-impl 
> <https://github.com/eclipse/jetty.project/tree/jetty-10.0.x/jetty-slf4j-impl>
> 
> This in turn has encouraged others to adopt slf4j 2.0 as well, including 
> the Eclipse IDE itself.
> This means we now have an OSGi manifest requirement that is being worked 
> out as I write this.
> 
> We have hundreds of thousands of installations of Eclipse Jetty 10+ 
> active around the world now, all with slf4j 2.0 running.
> 
> However, there's been a slow drum beat of criticism that says slf4j 
> looks like a dead project with an absent developer community.
> 
> I want to see slf4j survive and continue to be the awesome project we've 
> grown to love.
> 
> Is there anything you need help with?
> I'll be happy to help.
> Do you need help addressing or verifying anything from the JIRA issues 
> to progress?
> 
> Thanks again,
> Joakim Erdfelt (Eclipse Jetty committer)
> 

--
Ceki Gülcü