[
https://issues.apache.org/jira/browse/FINERACT-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103027#comment-17103027
]
Michael Vorburger commented on FINERACT-956:
--------------------------------------------
We should also fix this problem which one sees when running integration tests
in an IDE like Eclipse:
{code}SLF4J: No SLF4J providers were found.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details.
SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions prior to
1.8.
SLF4J: Ignoring binding found at
[jar:file:/home/vorburger/.gradle/caches/modules-2/files-2.1/ch.qos.logback/logback-classic/1.2.3/7c4f3c474fb2c041d8028740440937705ebb473a/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#ignoredBindings for an
explanation.{code}
> Logging missing / broken (since Spring Boot and/or Java 11 upgrade)
> -------------------------------------------------------------------
>
> Key: FINERACT-956
> URL: https://issues.apache.org/jira/browse/FINERACT-956
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Priority: Blocker
> Fix For: 1.4.0
>
>
> I think the logging got broken, since Spring Boot and/or Java 11 upgrade.
> At least it seems to me that there's usually more logging output when it
> starts...
> We could use this as the opportunity to adopt standard Spring Boot Logging
> config. This should give us neat coloured logging... ;-) -- I'm hoping that
> that out of the box also correctly integrates JUL logging and commons
> logging, and "standardize" those weird
> {{com.sun.jersey.spi.spring.container.SpringComponentProviderFactory
> registerSpringBeans}} we're currently seeing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
