It also might make sense to figure out how to accomplish this with the builder
api.
Ralph
> On May 6, 2020, at 10:03 PM, Ralph Goers wrote:
>
> When I started to read this I thought the conclusion was going to end with
> something more like:
>
> throw new ValidationException(logger.error("P
When I started to read this I thought the conclusion was going to end with
something more like:
throw new ValidationException(logger.error("Param %s must be in [%s-%s]", name,
low, high));
Or
logger.throw("Param %s must be in [%s-%s]", name, low, high),
ValidationException.class);
But I do
This would result in a large number of methods to be added most
likely, but you could potentially combine the logging with the
exception throwing:
logger.errorAndThrow( message, ValidationException.class );
which would log the message at the error level, and then use the given
class to construct
Potentially useful API update to look at here. Some sort of Logger that
throws an exception with the log message instead?
-- Forwarded message -
From: Norbert Kiesel
Date: Wed, 6 May 2020 at 12:59
Subject: [slf4j-user] Combined logging and throwing question
To: User list for the s
IIRC, the site builds as part of a normal build. Did you check the target
directory afterwards?
On Tue, May 5, 2020 at 16:52 Gary Gregory wrote:
> +1 but... while everything builds per the instructions I found, it would be
> nice to have something that tells you 'I ran tests and nothing blew up'
