cstamas commented on issue #1646: URL: https://github.com/apache/maven-resolver/issues/1646#issuecomment-3476388763
Well, this is not how one should resolve direct dependencies, as what happens in this case, is that you build the _whole dirty tree (transitive and all)_ only **to drop all of that** in 2nd part (flattening with filter applied). I mean, it works obviously, but this approach is very wasteful. The recommended way to resolve direct dependencies is basically just use `org.eclipse.aether.RepositorySystem#resolveArtifacts` method, with a list of direct dependencies, as this does only what it says, it does not collect and then drops all what it collected. The change is most probably due this change: https://github.com/apache/maven-resolver/commit/80e0d604f8fce59bb75739afa77cb4f1453445b2 Can you post some reproducer code snippet? As I still don't see how `null` comes into picture... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
