[
https://issues.apache.org/jira/browse/MRESOLVER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950763#comment-17950763
]
Per Nyfelt commented on MRESOLVER-718:
--------------------------------------
This could either look something like this (separate section, similar to the
pom layout)
<dependencyManagement id="dm1">
<dependencies>
<dependency groupId='org.junit' artifactId='junit-bom' version='5.12.2',
type='pom', scope='import'/>
</dependencies>
</dependencyManagement>
<dependencies id='d1' references='dm1'>
<dependency groupId='org.junit.jupiter' artifactId= 'junit-jupiter-engine'
scope='test'/>
<dependency groupId='org.junit.platform' artifactId=
'junit-platform-launcher' scope='test'/>
</dependencies>
or something like this (inline in the dependencies section)
<dependencies id='d1'>
<dependencyManagement groupId='org.junit' artifactId='junit-bom'
version='5.12.2', type='pom', scope='import'/>
<dependency groupId='org.junit.jupiter' artifactId= 'junit-jupiter-engine'
scope='test'/>
<dependency groupId='org.junit.platform' artifactId=
'junit-platform-launcher' scope='test'/>
</dependencies>
> Support dependencyManagement task
> ----------------------------------
>
> Key: MRESOLVER-718
> URL: https://issues.apache.org/jira/browse/MRESOLVER-718
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Ant Tasks
> Reporter: Per Nyfelt
> Priority: Major
>
> There does not seem to be a way to support BOM's
> Adding a dependency with the type pom and scope import to a dependencies
> section results in
> [resolve] Unknown scope 'import' for dependency
> To be in line with how boms are used in maven, it would make sense to add a
> dependencyManagement task where BOM's can be imported.
> Given such an import, it would also make sense to allow for coors without
> version (which currently throws an exception)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
