Bukama commented on code in PR #1726:
URL: https://github.com/apache/maven-site/pull/1726#discussion_r4327192685
##########
content/markdown/whatsnewinmaven4.md:
##########
@@ -138,7 +132,7 @@ The other types are new:
The `jar` and `processor` types use heuristic rules for deciding where to
place the JAR file, but the result is not always what the developer wants.
The types with `classpath-` or `modular-` prefix give control to the developer.
-**Limitation:** As of October 2025, only Maven Compiler Plugin (version
4.0.0-beta-3 and newer) complies with the new types.
+**Limitation:** As of Maven 4.0.0, only Maven Compiler Plugin (version
4.0.0-beta-3 and newer) complies with the new types.
Review Comment:
complies or compiles? I guess "compiles"
##########
content/markdown/whatsnewinmaven4.md:
##########
@@ -581,17 +556,52 @@ These are especially useful for applying consistent setup
and teardown logic aro
Together, these new phases provide a powerful and intuitive structure for
defining and customizing build behavior in complex Maven projects.
+## Configuration
+
+### Maven properties files
+
+Maven 4 introduces a layered properties system based on `maven.properties`
files.
+The main entry point is `${maven.home}/conf/maven.properties`, which loads
additional files from user-level
+(`~/.m2/maven-user.properties`) and project-level
(`${session.rootDirectory}/.mvn/maven-user.properties`) locations.
+Unlike standard Java properties files, Maven properties files are UTF-8
encoded, support file inclusion via the special
+`${includes}` key, and undergo property substitution with access to
environment variables, system properties, and
+session properties.
+
+This replaces the need to pass many `-D` flags on the command line or rely on
`MAVEN_OPTS` for configuration that
+should travel with the project.
+
+### Project-level settings
+
+Maven 4 supports project-level `settings.xml` files in
`${session.rootDirectory}/.mvn/settings.xml`, in addition to
Review Comment:
<3 I want Maven 4 at work :D
##########
content/markdown/whatsnewinmaven4.md:
##########
@@ -581,17 +556,52 @@ These are especially useful for applying consistent setup
and teardown logic aro
Together, these new phases provide a powerful and intuitive structure for
defining and customizing build behavior in complex Maven projects.
+## Configuration
+
+### Maven properties files
+
+Maven 4 introduces a layered properties system based on `maven.properties`
files.
+The main entry point is `${maven.home}/conf/maven.properties`, which loads
additional files from user-level
+(`~/.m2/maven-user.properties`) and project-level
(`${session.rootDirectory}/.mvn/maven-user.properties`) locations.
+Unlike standard Java properties files, Maven properties files are UTF-8
encoded, support file inclusion via the special
+`${includes}` key, and undergo property substitution with access to
environment variables, system properties, and
+session properties.
+
+This replaces the need to pass many `-D` flags on the command line or rely on
`MAVEN_OPTS` for configuration that
+should travel with the project.
+
+### Project-level settings
+
+Maven 4 supports project-level `settings.xml` files in
`${session.rootDirectory}/.mvn/settings.xml`, in addition to
+the existing user-level (`~/.m2/settings.xml`) and installation-level
(`${maven.home}/conf/settings.xml`) settings.
+This allows teams to share repository, mirror, and server configurations as
part of the project source code.
+
+### Auto CI detection
+
+Maven 4 automatically detects common CI environments and adjusts its behavior
accordingly.
Review Comment:
We should mentioned (either here or a new page, cause I think
https://maven.apache.org/guides/mini/guide-maven-ci-friendly.html is not
fitting for this) what "common CI environments" means
--
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]
