Le mar. 21 févr. 2023 à 21:16, Elliotte Rusty Harold a
écrit :
> On Tue, Feb 21, 2023 at 3:07 PM Romain Manni-Bucau
> wrote:
>
> > In terms of default I think default should match the most common case and
> > downloads is not a common case for maven but a very troublesome one when
> it
> > fails
Cancelling the vote.
I'll revert the velocity upgrade and cut a new release.
--
Guillaume Nodet
On Tue, Feb 21, 2023 at 3:07 PM Romain Manni-Bucau
wrote:
> In terms of default I think default should match the most common case and
> downloads is not a common case for maven but a very troublesome one when it
> fails or hangs and not logging anything means maven hangs for end user
> without id
What I dislike with -vvv or --log-level=[debug|info|...] is your control is
basically all or nothing (maven -q/-X, podman, curl i'm looking at your
shortcuts ;)) whereas being able to configure log level per logger name on
the CLI (ideally with completion) enables you to configure exactly what you
A common way to control "verbosity" in commandline application is having:
default : as silent as possible
-v : show some level of output (e.g. "Downloading dependencies ...")
-vv : show more (e.g. Start downloading / stop downloading)
-vvv : even more
This could easily adopted for other areas
A general pattern I notice in discussions of excessive logging — not
just here and not only involving Maven — is to describe a scenario in
which a certain log message is useful. This is not hard to do but does
not justify the log message. Instead it is necessary to estimate how
often that log messa
Hi Elliotte,
On Mon, 20 Feb 2023 at 19:51, Elliotte Rusty Harold wrote:
> I don't believe anyone reads most of these messages most of the time.
> In fact, I'd venture that well more than 99% of them are never read by
> anyone.
Some people started reading these after Log4Shell. On StackOverflow
q
