gnodet commented on code in PR #451:
URL: https://github.com/apache/maven-site/pull/451#discussion_r1332690000
##########
content/apt/guides/introduction/introduction-to-dependency-mechanism.apt:
##########
@@ -822,6 +822,48 @@ Introduction to the Dependency Mechanism
artifact may not have a version specified. (This should be considered a
best practice in any case as it
keeps the versions of artifacts from changing from one build to the next).
+Starting from Maven 4.0, a new specific BOM packaging has been introduced.
+It allows defining a BOMs which are not used as parent in a project leveraging
+the newer 4.1.0 model, while still providing full compatibility with Maven 3.X
+clients and projects. This BOM packaging is translated into a more usual POM
+packaging at installation / deployment time, leveraging the build/consumer POM
+feature from Maven 4. This thus provides full compatibility with Maven 3.x.
Review Comment:
What I was referring to is just `<packaging>bom</packaging>` which is
translated with to `<packaging>pom</packaging>` in the consumer pom, so that
it can be consumed using Maven 3.
This is in addition to the usual build/consumer transformation. The PR
https://github.com/apache/maven/pull/1247 proposed to make a big difference
between POMs using the `pom` packaging (which are used as parents) and other
artifacts (which are consumed, but not as parents). The parents must keep all
the build informations, while it can be removed from consumed artifacts. This
will allow upgrading the model with new features at build time without having
any impact on consumed artifacts (because their consumer POM will be translated
into a 4.0.0 model).
--
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]
