[
https://issues.apache.org/jira/browse/MRESOLVER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953735#comment-17953735
]
Tamas Cservenak commented on MRESOLVER-718:
-------------------------------------------
Just to add to this :)
You may get good use of jbang + toolbox:
{noformat}
[cstamas@angeleyes ~]$ jbang toolbox@maveniverse classpath
--boms=org.junit:junit-bom:5.12.2 org.junit.jupiter:junit-jupiter-api
/home/cstamas/.m2/repository-oss/org/junit/jupiter/junit-jupiter-api/5.12.2/junit-jupiter-api-5.12.2.jar:/home/cstamas/.m2/repository-oss/org/opentest4j/opentest4j/1.3.0/opentest4j-1.3.0.jar:/home/cstamas/.m2/repository-oss/org/junit/platform/junit-platform-commons/1.12.2/junit-platform-commons-1.12.2.jar:/home/cstamas/.m2/repository-oss/org/apiguardian/apiguardian-api/1.1.2/apiguardian-api-1.1.2.jar
[cstamas@angeleyes ~]$ {noformat}
> 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 when declaring the
> dependencies in the build.xml only (not relying on an external pom file)
> 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 coords without
> version (which currently throws an exception)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
