[
https://issues.apache.org/jira/browse/MRESOLVER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953721#comment-17953721
]
Tamas Cservenak commented on MRESOLVER-718:
-------------------------------------------
Sadly, "import" scope is an ugly hack that is done in Maven: Resolver have no
idea about it! It all happens in Maven, and the whole logic not even enters
Resolver. Plus, the whole code in Maven doing this is not quite reusable, so it
would mean "cleanroom reimplementation" here (think recursive imports, etc).
> 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)
