Am 2021-08-01 um 13:03 schrieb Michael Osipov:
Am 2021-08-01 um 11:04 schrieb Romain Manni-Bucau:
Le dim. 1 août 2021 à 01:22, Stephen Connolly <
[email protected]> a écrit :
I’m fine with a breaking change.
I also think batch mode debugging is a special case, we could go with
—batch-debug
Both options are transversal IMHO so let it be.
If you run in debug without custom jvm options (ie --debug or
mvnDebug) it
means for maven "hang", no need to make it complicated/contextual.
If you want something finer do as today, use MAVEN_OPTS.
Sigh, I need to agree with Romain here. mvnDebug did not care about -B
being passed because it comes before any main class. I think you can try
hard to accomondate all cases, but you still will fail with edge cases
anyway.
Make it unconditional from "mvnDebug" to "mvn --debug" since it is only
a small step.
I think we can make it in two steps: In alpha-1 we still accept --debug,
but issue a warning that it is deprecated in favor of --verbose and will
be repurposed in an upcoming alpha. For those who will deploy the first
alpha to a CI server must have an extra look at builds because they
might break anyway. I also expect any CI system to highlight warnings.
Moreover, we can add add a general timeout of some minutes (e.g., 3
min). If should be enough for a developer to attach to a VM or just fail
the build in CI to get developer's attention to replace --debug with -X
or --verbose in the future.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
