-
There is currently no logging available and all errors are dropped silently. This needs to be addressed.
-
```
It is much better to use slf4j than commons logging. It is possible for
everyone to stick to their chosen implementation. As most frameworks use slf4j
it is quite a hassle to work around commons…
-
```
It is much better to use slf4j than commons logging. It is possible for
everyone to stick to their chosen implementation. As most frameworks use slf4j
it is quite a hassle to work around commons…
-
```
It is much better to use slf4j than commons logging. It is possible for
everyone to stick to their chosen implementation. As most frameworks use slf4j
it is quite a hassle to work around commons…
-
Expected behaviour:
Put log4j config to src/main/resources to be able to configure logging.
Actual behaviour:
Either version of config https://logging.apache.org/log4j/2.x/manual/configuration.html…
-
https://github.com/aws/aws-lambda-java-libs/blob/master/aws-lambda-java-runtime-interface-client/src/main/java/com/amazonaws/services/lambda/runtime/api/client/EventHandlerLoader.java#L888
Here, co…
-
```
It is much better to use slf4j than commons logging. It is possible for
everyone to stick to their chosen implementation. As most frameworks use slf4j
it is quite a hassle to work around commons…
-
```
It is much better to use slf4j than commons logging. It is possible for
everyone to stick to their chosen implementation. As most frameworks use slf4j
it is quite a hassle to work around commons…
-
```
It is much better to use slf4j than commons logging. It is possible for
everyone to stick to their chosen implementation. As most frameworks use slf4j
it is quite a hassle to work around commons…
-
```
It is much better to use slf4j than commons logging. It is possible for
everyone to stick to their chosen implementation. As most frameworks use slf4j
it is quite a hassle to work around commons…