Use batch mode by default

[anthonydahanne]

• maven is very verbose in CI if you don't use this option

Summary

The batch mode option fits very well with CI tooling

Use Cases

Take this build for example:

• Without batch mode, super verbose, for no added value:
  https://github.com/anthonydahanne/java-applications-containerized/runs/1975032196

• With batch mode, much more concise
  https://github.com/anthonydahanne/java-applications-containerized/runs/1975054421

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have reviewed the styleguide for guidance on my code quality.

[ekcasey]

@anthonydahanne This makes sense. But I wonder if we want to append --batch-mode to the arguments only if stdout is not a tty? There may be cases where output is written to an actual TTY device and it would be nice to see progress bars and colors.

Related:

• Run Containers with Mirrored TTY buildpacks/pack#493
• Not a tty actions/runner#241

[anthonydahanne]

oh indeed, that's a good idea to detect the stdout type!
héhé - buildpacks are all about detection !