Hi all, When setting up GitHub Actions for Maven (core) two weeks ago, I initially forgot to enable the -B/--batch-mode flag. While this gave no issues and was easy to fix, it could be avoided by detecting if Maven is executed on popular CI environments and in that case automatically enabling batch mode. Popular CI tools such as GitHub Actions [1] and GitLab CI [2] provide predefined environment variables, which could be used for this purpose. When this would automatically activate, we log this on INFO level. We would also need an option to turn batch-mode off to override this automatic behavior.
The reason why I haven't created a JIRA issue yet is because I realize I do not know if this fits the usual workings for Maven. Based on best guesses (de-)activating certain functionality can in my vision be a quality-of-life improvement for our users. On the other hand I have the feeling currently Maven does favor users to explicitly set their CLI flags. Just wanted to know your opinion. If I get positive feedback I will create a JIRA issue. Otherwise we can consider alternatives (only log a hint: "CI run detected, did you want to run in --batch-mode?") or leave it like it is. Thanks, Martin [1] https://docs.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables [2] https://docs.gitlab.com/ee/ci/variables/predefined_variables.html
