slachiewicz opened a new pull request, #1791: URL: https://github.com/apache/maven-site/pull/1791
Fills gaps 15, 16, 18 and 20 from Martijn Dashorst's list of places where the documentation and Maven disagree ([discrepancies page](https://github.com/dashorst/maven-site/blob/diataxis-demo/jekyll/pages/discrepancies.md)). * *Configuring Apache Maven* names both settings files and, for Maven 4, `.mvn/settings.xml`; says which of `MAVEN_OPTS` and `.mvn/jvm.config` wins on each line; and adds `MAVEN_REPO_CENTRAL` (or `maven.repo.central`) and the `~/.m2/extensions.xml` and `conf/extensions.xml` files of 3.10.0. * *Settings Reference* adds Maven 4's project settings, which ignore `localRepository` and credentials, with warnings only under `-e`. * *Configuring a proxy* no longer says that a later release may store passwords securely; proxy passwords can be encrypted like server passwords. Verified on 3.9.16, 3.10.0 and 4.0.0-rc-7: * `-Dprobe` in both places → `MAVEN_OPTS` wins on 3.x, `jvm.config` on 4; * an unresolvable extension in `~/.m2/extensions.xml` or `conf/extensions.xml` → resolution fails on 3.10.0 and 4 (file read), not on 3.9; * `MAVEN_REPO_CENTRAL` and `-Dmaven.repo.central` → downloads go to the given URL on 3.10.0 and 4, not on 3.9; * `.mvn/settings.xml` → its active profile applies on 4, not on 3.10.0; `localRepository` and `<server>` credentials are dropped, and the warnings appear only with `-e`; * an encrypted proxy password through a local proxy that requires Basic authentication → the proxy receives the decrypted credentials, BUILD SUCCESS on all three lines. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
