[
https://issues.apache.org/jira/browse/MRESOLVER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953740#comment-17953740
]
Tamas Cservenak commented on MRESOLVER-718:
-------------------------------------------
Combined copy w/ flat (flat directory) sink:
{noformat}
[cstamas@angeleyes MRESOLVER-718]$ ll -a
total 0
drwxr-xr-x. 1 cstamas cstamas 0 May 23 18:38 .
drwxr-xr-x. 1 cstamas cstamas 2108 May 23 18:36 ..
[cstamas@angeleyes MRESOLVER-718]$ tree -a
.0 directories, 0 files
[cstamas@angeleyes MRESOLVER-718]$ jbang toolbox@maveniverse copy-transitive
--boms=org.junit:junit-bom:5.12.2 "flat(lib)"
org.junit.jupiter:junit-jupiter-engine,org.junit.platform:junit-platform-launcher
Copied 11 artifacts
[cstamas@angeleyes MRESOLVER-718]$ tree
.
└── lib
├── apiguardian-api-1.1.2.jar
├── junit-jupiter-api-5.12.2.jar
├── junit-jupiter-engine-5.12.2.jar
├── junit-platform-commons-1.12.2.jar
├── junit-platform-engine-1.12.2.jar
├── junit-platform-launcher-1.12.2.jar
└── opentest4j-1.3.0.jar2 directories, 7 files
[cstamas@angeleyes MRESOLVER-718]$ {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)
