[
https://issues.apache.org/jira/browse/MRESOLVER-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607541#comment-17607541
]
Tamás Cservenák commented on MRESOLVER-259:
-------------------------------------------
Unsure is this doable in this way.... at least not in resolver but maybe using
some trick: resolver always cache and expects always to have local repository,
there is no way around it. Now, maybe you create some "ramdisk" volume or so?
Resolver is not there yet, but would be cool to be able to use it with stuf
like https://github.com/google/jimfs
> 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: New Feature
> 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.10#820010)
