[
https://issues.apache.org/jira/browse/MRESOLVER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953724#comment-17953724
]
Per Nyfelt commented on MRESOLVER-718:
--------------------------------------
I found a quite decent workaround that is supported today i.e. to generate a
pom and "register" it with the pom task ( <pom
file="${basedir}/target/myProject.pom /> ) before the resolve task is called.
For my case, I added a dependencyManagement type and created a createPom task
that creates the pom file and populates the dependency management and
dependencies sections respectively based on the id refs given to the createPom
task as parameters. The result is (i think) much cleaner/better than the
equivalent ant + ivy combination.
> 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)
