You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/05/21 16:04:00 UTC

[jira] [Commented] (MRESOLVER-259) Enable the option of getting all dependencies names (including poms) without downloading them

    [ https://issues.apache.org/jira/browse/MRESOLVER-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540450#comment-17540450 ] 

Michael Osipov commented on MRESOLVER-259:
------------------------------------------

And where is the bug?

> Enable the option of getting all dependencies names (including poms) without downloading them
> ---------------------------------------------------------------------------------------------
>
>                 Key: MRESOLVER-259
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-259
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: Resolver
>            Reporter: robjea
>            Priority: Major
>
> I may just not know how to perform this (that's pretty hard learning to use this awesome library without any documentation available - just through digging in the code).
> Anyway, I'm building a dependencies resolving system, and for this, I need to get all of the transitive jars and *poms* needed for resolving a single artifact. I was looking at the demo on the `GetDependencyHierarchy` class, but when I use a function like `dependencyResult.getRequest().getCollectRequest().getManagedDependencies()` I only get a list of artifacts. No poms. I really need to list these poms and the only way I've figured out to do that was to add them from the listener class (through events). This is a pretty dirty way of doing this and I wonder if there's a way of getting the dependencies list including poms in an easier and cleaner way?
> My second request is to be able to do this without actually installing them. I don't need them locally and I just want this list. I currently delete the local folder after each resolving cycle, but this is dirty. Is there a way to resolve dependency and only get the list of the resolving result? Without some `localRepositoryManager`.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)