There was an interesting question on Twitter the other day,
why beside configuration there had never been a JSR for
logging which is also a fundamental aspect of many enterprise
There was in the very early days of the JCP:
java.util.logging never was vendor-neutral or extendable and
unlike the Collections Framework which has many different
implementations also at Eclipse I'm not aware any alternate
implementation outside the JDK ever existed.
Markus Eisele thought about this when he worked at Red Hat
for the first time, several years ago about a decade or so.
However, the idea never got beyond initial discussions with
involved vendors. And from what I heard back then it was a
similar kind of vanity and pride by authors of several
frameworks like Log4J, LogBack/SLF4J or Apache Commons Logging
and of course the JDK team behind JUL.
Every committer or team insisted, only their project could
be the RI for such JSR, so eventually Markus gave up the idea.
Interestingly the JDK picked up the idea mostly to make
itself a little more modular and simplify the dependency graph
with Java 9: http://openjdk.java.net/jeps/264
I am not sure, what exact TCK support exists for this API,
but it aims to be easily adoptable by applications which use
external logging framework, such as SLF4J or Log4J, so that'll
have to do for now, and it does not seem like a Jakarta
standard or MP feature is really worth the effort in this