[ https://issues.apache.org/jira/browse/MNG-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152237#comment-15152237 ]
Christian Schulte commented on MNG-5971: ---------------------------------------- We cannot change the way the {{import}} scope is defined. We could introduce a new scope {{include}} behaving exactly the way you describe. Since that scope would be processed very early (before inheritance and interpolation), you cannot use any features like property expansion. {code} <dependency> <groupId>must be a constant</groupId> <artifactId>must be a constant</artifactId> <version>must be a constant</version> <scope>include</scope> <type>pom</type> </dependency> {code} Will provide a 3.4.0-SNAPSHOT later today. > Dependency management in a child project cannot override a version using a BOM > ------------------------------------------------------------------------------ > > Key: MNG-5971 > URL: https://issues.apache.org/jira/browse/MNG-5971 > Project: Maven > Issue Type: Wish > Components: Dependencies > Affects Versions: 3.3.3 > Reporter: Stephane Nicoll > Priority: Trivial > Labels: close-pending > > When a project extends from a parent with a {{dependencyManagement}} section, > it is not always possible to properly override (and align) the version to use > for a group of dependencies. > We typically use Bill Of Materials to gather a group of modules and make sure > their versions are consistent. > The following project demonstrates the issue: > https://github.com/snicoll-scratches/maven-dependency-management > The first commit is a working use case where the parent uses a bom with > version A and we use the same bom with version B in the child. Version B is > used as expected. > The second commit demonstrates the faulty scenario. Rather than using a bom > in the parent, we use a direct dependency (provided by that bom). We still > use the bom with a different version. In that case all the dependencies but > the one provided by the parent are overridden (leading to mixed versions for > the dependencies provided by the BOM). > It looks like the distance is still used to compute the version while the > graph of dependencies should be flatten at each step for a proper override. > Thoughts? Thanks! -- This message was sent by Atlassian JIRA (v6.3.4#6332)