Am 2020-07-13 um 08:10 schrieb Romain Manni-Bucau:
Le dim. 12 juil. 2020 à 22:13, Michael Osipov <[email protected]> a
écrit :
Am 2020-07-12 um 21:35 schrieb Maarten Mulders:
Although no formal standards, many cloud-based CI environments agreed
upon setting CI=true, and I think also Jenkins does that. It might be a
relatively simple way to detect most CI environments.
The next question is what Maven should do with that information. I feel
like informing the user is more in the Maven spirit (just as the fact
that 3.7.0 warns when plugin versions aren't locked). Something like
"you typically want to set -B in this case". Setting flags the user
isn't aware of feels a bit odd to me.
Don't limit your mind to CI only, please.
Here is the most basic use case for isatty() detection:
$ mvn ... > out
$ mvn ... | grep foo
If nothing passed, the system shall assume --non-interactive.
Why? You can inject input there and you can also use colors.
No, this expected behavior for every decent Unix tool for decades. If
you are not interactive, you have to force it with --force-interactive.
See grep, tree, svn, git, ls etc. I don't epect Maven to be different here.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
