I’m fine with a breaking change.
I also think batch mode debugging is a special case, we could go with
—batch-debug
If you really want to debug batch mode and that way —debug can be
incompatible with —batch and then we don’t worry about it
On Sat 31 Jul 2021 at 16:06, Michael Osipov wrote:
>
Hi all,
I would like to suggest to write a small specification of the feature
you brought up. I have somethink in mind similar to the JEP process for
Java.
I could create a repo at Github, so that we can work there on the
feature description and ask other people to review it or to
Well, I have just tried.
Not providing a timeout is just like providing timeout=0. The socket
will wait forever.
If your provide a timeout and don't connect after a timeout, this will
happen:
Listening for transport dt_socket at address: 8000
ERROR: transport error 203: timed out waiting for
Le sam. 31 juil. 2021 à 16:48, Michael Osipov a
écrit :
> Am 2021-07-31 um 16:40 schrieb Romain Manni-Bucau:
> > Open question: if mvnDebug stays (i am all for it), why deprecating it?
> It
> > is very useful for all dev using embed plugins (most of them) like jetty,
> > tomee, tomcat,
Am 2021-07-31 um 16:40 schrieb Romain Manni-Bucau:
Open question: if mvnDebug stays (i am all for it), why deprecating it? It
is very useful for all dev using embed plugins (most of them) like jetty,
tomee, tomcat, meecrowave, renders, etc
What is the problem you see? It add unnecessary
Open question: if mvnDebug stays (i am all for it), why deprecating it? It
is very useful for all dev using embed plugins (most of them) like jetty,
tomee, tomcat, meecrowave, renders, etc
Le sam. 31 juil. 2021 à 16:32, Robert Scholte a
écrit :
> CI can have multiple Maven versions.
> Mistakes
CI can have multiple Maven versions.
Mistakes will happen: users might add --debug assuming verbose logging.
With an Environment Variable the CI server can globally suppress the option to
debug.
I'm also fine with a NO_DEBUG option, but I'd like to have a global way to
suppress the impact.
Am 2021-07-31 um 11:22 schrieb Robert Scholte:
Right, it is suspend, I misinterpreted the description of server.
Can we introduce an environment variable for it, so CI servers can set it to 0?
Let me summarize:
If --debug is passed everything will work as before: wait forever
If --debug
Thx for the clarification.
Regards
Clemens
Am 31. Juli 2021 10:58:07 MESZ schrieb Robert Scholte :
>The discussion is about using --debug -B (combination of these 2 flags). With
>Maven 3 this meant batch-mode + debug level logging.
>The proposal for Maven 4 is to change debug level logging to
Right, it is suspend, I misinterpreted the description of server.
Can we introduce an environment variable for it, so CI servers can set it to 0?
Robert
On 30-7-2021 21:46:46, Michael Osipov wrote:
I guess you mean suspend and not server.
Your idea may work, but still is problematic. If the
The discussion is about using --debug -B (combination of these 2 flags). With
Maven 3 this meant batch-mode + debug level logging.
The proposal for Maven 4 is to change debug level logging to --verbose/-X and
redefine --debug for debugging instead of mvnDebug.
So if you're only using -B there's
11 matches
Mail list logo
