mvnw output does not respect --quiet
- Dominant language
- Java
- Stars
- 254
- Forks
- 78
- Avg merge
- 5h 26m
- Merged PRs (30d)
- 2
Description
### Affected version
3.3.4
### Bug description
We happened to remove a maven build statement in our GitLab CI before extracting a version number from our pom.xml, and our CI started erroring when trying to upload dotenv artifacts.
```
$ mvnw -Dexpression=project.version -q -DforceStdout help:evaluate
[WARNING] Using an insecure connection to download the Maven distribution. Please consider using HTTPS.
0.16.0-SNAPSHOT
```
_Note that the -DforceStdout does not change anything in this regard._
I guess that is because the wrapper does not respect the [--quiet flag](https://maven.apache.org/ref/3.9.16/maven-embedder/cli.html), would that be possible and in its scope ?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported `mvnw -Dexpression=project.version -q -DforceStdout help:evaluate` command and trace how the wrapper handles the quiet option before invoking Maven. Compare the output with and without `-q`; done means the version remains available while the insecure-connection warning is suppressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100