This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 68b998b5 Document settings and extension locations, MAVEN_REPO_CENTRAL 
and encrypted proxy passwords
68b998b5 is described below

commit 68b998b5fe9b6d1636303cca300590dec5fa0f2c
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Mon Nov 2 12:44:32 2026 +0000

    Document settings and extension locations, MAVEN_REPO_CENTRAL and encrypted 
proxy passwords
---
 content/markdown/configure.md                 | 18 ++++++++++++++++--
 content/markdown/guides/mini/guide-proxies.md |  2 +-
 content/markdown/settings.md                  |  4 ++++
 3 files changed, 21 insertions(+), 3 deletions(-)

diff --git a/content/markdown/configure.md b/content/markdown/configure.md
index 9a339e3d..50ad9a82 100644
--- a/content/markdown/configure.md
+++ b/content/markdown/configure.md
@@ -28,16 +28,26 @@ This variable contains parameters used to start up the JVM 
running Maven and
 can be used to supply additional options to it. E.g. JVM memory
 settings can be defined with the value `-Xms256m -Xmx512m`.
 
+When an option is set both here and in `.mvn/jvm.config`, Maven 3 uses the 
value from
+`MAVEN_OPTS` and Maven 4 the one from `jvm.config`.
+
 ## `MAVEN_ARGS` environment variable:
 
 Starting with Maven 3.9.0, this variable contains arguments passed to Maven 
before
 CLI arguments. E.g., options and goals could be defined with the value
 `-B -V checkstyle:checkstyle`.
 
+## `MAVEN_REPO_CENTRAL` environment variable:
+
+Starting with Maven 3.10.0, this variable replaces the URL of the central 
repository,
+`https://repo.maven.apache.org/maven2`, for example with the URL of a 
repository manager. The `maven.repo.central`
+user property does the same.
+
 ## `settings.xml` file:
 
-Located in USER_HOME/.m2, the settings files is designed to contain any
-configuration for Maven usage across projects.
+The settings files are designed to contain any configuration for Maven usage 
across projects. Maven reads the
+installation settings in `${maven.home}/conf/settings.xml` and the user 
settings in `${user.home}/.m2/settings.xml`;
+Maven 4 also reads project settings in `.mvn/settings.xml`. See the [Settings 
Reference](./settings.html).
 
 ## `.mvn` directory:
 
@@ -74,6 +84,10 @@ From now on this can be done much more simpler and more 
Maven like way. Define a
 
 Now you can simply use an extension by defining the usual maven coordinates 
groupId, artifactId, version as any other artifact. Furthermore, all transitive 
dependencies of those extensions will automatically being downloaded from your 
repository. So no need to create a shaded artifact anymore.
 
+Starting with Maven 3.10.0, Maven also loads the extensions listed in 
`${user.home}/.m2/extensions.xml`, for all of
+your builds, and in `${maven.home}/conf/extensions.xml`, for every build that 
uses that Maven installation. Both files
+have the same format as `.mvn/extensions.xml`.
+
 ### `.mvn/maven.config` file:
 
 It’s really hard to define a general set of options for calling the maven 
command line. Starting with Maven 3.3.1+, this could be solved by
diff --git a/content/markdown/guides/mini/guide-proxies.md 
b/content/markdown/guides/mini/guide-proxies.md
index 329cb26e..3435b3b7 100644
--- a/content/markdown/guides/mini/guide-proxies.md
+++ b/content/markdown/guides/mini/guide-proxies.md
@@ -19,7 +19,7 @@ under the License.
 
 # Configuring a proxy
 
-You can configure a proxy to use for some or all of your HTTP requests with 
Maven. The username and password are only required if your proxy requires basic 
authentication (note that later releases may support storing your passwords in 
a secured keystore - in the mean time, please ensure your settings.xml file 
(usually ${user.home}/.m2/settings.xml) is secured with permissions appropriate 
for your operating system).
+You can configure a proxy to use for some or all of your HTTP requests with 
Maven. The username and password are only required if your proxy requires basic 
authentication. You can [encrypt the password](./guide-encryption.html) like a 
server password; either way, make sure your settings.xml file (usually 
${user.home}/.m2/settings.xml) is secured with permissions appropriate for your 
operating system.
 
 The `nonProxyHosts` setting accepts wild cards, and each host not to proxy is 
separated by the | character. This matches the JDK configuration equivalent.
 
diff --git a/content/markdown/settings.md b/content/markdown/settings.md
index 44afe147..e61f2129 100644
--- a/content/markdown/settings.md
+++ b/content/markdown/settings.md
@@ -41,6 +41,10 @@ The former `settings.xml` is also called global settings, 
the latter
 their contents get merged, with the user-specific `settings.xml` being
 dominant.
 
+Maven 4 also reads project settings from `.mvn/settings.xml` in the project's 
top level directory. Because that file
+is part of the project, Maven ignores the elements that belong to you rather 
than to the project, such as
+`localRepository` and server credentials. It warns about them only when run 
with `-e`.
+
 Tip: If you need to create user-specific settings from scratch, it's
 easiest to copy the global settings from your Maven installation to your
 `${user.home}/.m2` directory. Maven's default `settings.xml` is a

Reply via email to