[
https://issues.apache.org/jira/browse/MRESOLVER-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540455#comment-17540455
]
robjea commented on MRESOLVER-259:
----------------------------------
I'm fine with reading POMs of course, but:
# This doesn't mean downloading jars (that resolving action can get completed
without them just fine)
# This doesn't mean saving them. My Java application can hold objects that
represent POM files without persisting them on disk (and when the app will go
down they will get deleted because they have only been kept on the RAM).
So of course that's physically possible.
Whats your opinion regarding the first point? Do you know of a way to get a
list of jars *and poms* (even if they'll get persisted on disk)?
> 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.7#820007)
