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

Bukama 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 6bd70cba Update pages to reflect additions are in 4.2 since there 
won't be a 4.1 (#1826)
6bd70cba is described below

commit 6bd70cbaf11edcdb8cf5859c978e76abd1d66bf1
Author: Matthias Bünger <[email protected]>
AuthorDate: Thu Nov 12 17:14:40 2026 +0100

    Update pages to reflect additions are in 4.2 since there won't be a 4.1 
(#1826)
---
 content/markdown/guides/introduction/introduction-to-profiles.md | 2 +-
 content/markdown/guides/mini/guide-mixins.md                     | 6 +++---
 content/markdown/tools/index.md                                  | 2 +-
 content/markdown/tools/mvnval.md                                 | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/markdown/guides/introduction/introduction-to-profiles.md 
b/content/markdown/guides/introduction/introduction-to-profiles.md
index 8d9e1685..6d8c83e8 100644
--- a/content/markdown/guides/introduction/introduction-to-profiles.md
+++ b/content/markdown/guides/introduction/introduction-to-profiles.md
@@ -362,7 +362,7 @@ Different implicit activation types can be combined in one 
profile. The profile
 
 #### Cascading profile activation
 
-_Since Maven 4.1._
+_Since Maven 4.2._
 
 When a POM profile is activated and defines `<properties>`, those properties 
are immediately available to trigger the activation of other profiles in the 
same POM. Maven iterates through the remaining inactive profiles until no new 
profiles are activated (a fixed-point is reached). This is called **cascading 
profile activation**.
 
diff --git a/content/markdown/guides/mini/guide-mixins.md 
b/content/markdown/guides/mini/guide-mixins.md
index 50fe21dc..e4b03111 100644
--- a/content/markdown/guides/mini/guide-mixins.md
+++ b/content/markdown/guides/mini/guide-mixins.md
@@ -16,9 +16,9 @@ KIND, either express or implied.  See the License for the
 specific language governing permissions and limitations
 under the License.
 -->
-# Maven Mixins (Maven 4.1)
+# Maven Mixins (Maven 4.2.0)
 
-Maven Mixins will provide (in Maven 4.1) a powerful mechanism for sharing 
common POM configuration across multiple projects without the limitations of 
traditional inheritance. Mixins allow you to compose your project configuration 
from multiple sources, promoting better code reuse and maintainability.
+Maven Mixins will provide (in Maven 4.2.0) a powerful mechanism for sharing 
common POM configuration across multiple projects without the limitations of 
traditional inheritance. Mixins allow you to compose your project configuration 
from multiple sources, promoting better code reuse and maintainability.
 
 ## Overview
 
@@ -64,7 +64,7 @@ Mixins are declared in the `<mixins>` section of your POM:
 
 ### Model Version Requirement
 
-Mixins require **model version 4.2.0** (introduced with Maven 4.1.0) or 
higher. This new model version was introduced specifically to support the 
mixins feature while maintaining backward compatibility.
+Mixins require **model version 4.2.0** (introduced with Maven 4.2.0) or 
higher. This new model version was introduced specifically to support the 
mixins feature while maintaining backward compatibility.
 
 ## Creating Mixin POMs
 
diff --git a/content/markdown/tools/index.md b/content/markdown/tools/index.md
index e8a86d42..bd77972f 100644
--- a/content/markdown/tools/index.md
+++ b/content/markdown/tools/index.md
@@ -28,7 +28,7 @@ The pages in this section will give information about 
additional Maven tools, wh
 | [Maven Daemon](./mvnd.html)          | `mvnd` speeds up Maven builds using 
daemon process management and caching.                                          
                                     | [Github][1]         |
 | [Maven Shell](./mvnsh.html)          | `mvnsh` is a shell that permits reuse 
of a single JVM during development.  It's a built-in tool, shipped with Maven.  
                                   | -                   |
 | [Maven Upgrade Tool](./mvnup.html)            | `mvnup` allows you to 
automatically upgrade your Maven project to newer Maven versions, starting with 
Maven 4. It's a built-in tool, shipped with Maven.       | -                   |
-| [Maven POM Validation Tool](./mvnval.html)    | `mvnval` validates POM files 
and reports all problems without running a build. It's a built-in tool, shipped 
with Maven 4.1.0.                                 | -                   |
+| [Maven POM Validation Tool](./mvnval.html)    | `mvnval` validates POM files 
and reports all problems without running a build. It's a built-in tool, shipped 
with Maven 4.2.0.                                 | -                   |
 | [Maven Wrapper](./mavenwrapper.html)          | `mvnw` ensures that a 
project is built with a desired Maven version and/or JDK by automatically 
downloading them.                                              | [Project's 
site][2] |
 
 [1]: https://github.com/apache/maven-mvnd
diff --git a/content/markdown/tools/mvnval.md b/content/markdown/tools/mvnval.md
index 95e1e0ca..ea4b369f 100644
--- a/content/markdown/tools/mvnval.md
+++ b/content/markdown/tools/mvnval.md
@@ -20,7 +20,7 @@ under the License.
 -->
 
 The Maven POM Validation Tool (`mvnval`) validates POM files and reports all 
problems without
-running a build. It is a built-in tool, shipped with Maven 4.1.0.
+running a build. It is a built-in tool, shipped with Maven 4.2.0.
 
 <!--MACRO{toc|fromDepth=2}-->
 

Reply via email to