[
https://issues.apache.org/jira/browse/MNGSITE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise moved MNG-6989 to MNGSITE-460:
--------------------------------------------------
Component/s: (was: Documentation: Introductions)
Key: MNGSITE-460 (was: MNG-6989)
Affects Version/s: (was: 3.6.3)
Project: Maven Project Web Site (was: Maven)
> The page "Introduction to the Dependency Mechanism" shows deprecated practices
> ------------------------------------------------------------------------------
>
> Key: MNGSITE-460
> URL: https://issues.apache.org/jira/browse/MNGSITE-460
> Project: Maven Project Web Site
> Issue Type: Bug
> Reporter: Mikaël Barbero
> Priority: Major
>
> Page URL:
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> The section "[Bill of
> Materials|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#bill-of-materials-bom-poms]";
> explains that one should use some properties to define submodules versions
> (e.g., project1Version). Defining versions this way lead to publish pom files
> with $variable in in their <version>. This a bad practice that Maven warns
> about during builds. I think this should not be advocated in an introduction
> guide. AFAICT, the "standard" way for handling a bom setup is to have all
> modules inheriting their versions from the parent pom.
> If one committer is willing to point me where the code of this guide is
> stored, I may be able to submit a patch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
