[
https://issues.apache.org/jira/browse/MRESOLVER-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738798#comment-17738798
]
ASF GitHub Bot commented on MRESOLVER-376:
------------------------------------------
cstamas opened a new pull request, #309:
URL: https://github.com/apache/maven-resolver/pull/309
The code uses Artifact to key (forever during collection) the read artifact
descriptors, but, this is not always what we want.
Example: ArtifactDescriptorReader when reads a relocated artifact, it will
use RelocatedArtifact (in maven-resolver-provider) as result.artifact, and BF
use this artifact as key. But, this artifact will be key of relocation target,
while the descriptor is the descriptor of original (relocated) artifact. As it
gets into (inner) async resolver cache, it will stay there forever. But alas,
we next ask for relocation target decriptor, that as can be seen, use same
(key-wise, or GAV wise) key as the relocated artifact, and nothing happens, as
computeIfAbsent does not compute (as it is present), and we fall into endless
loop.
---
https://issues.apache.org/jira/browse/MRESOLVER-376
> StackOverflowError at BfDependencyCollector.processDependency
> -------------------------------------------------------------
>
> Key: MRESOLVER-376
> URL: https://issues.apache.org/jira/browse/MRESOLVER-376
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Affects Versions: 1.9.13
> Reporter: Snjezana Peco
> Priority: Major
> Fix For: 1.9.14
>
>
> Steps to reproduce:
> {code:java}
> $ mvn -v
> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f))
> $ git clone g...@github.com:snowflakedb/snowflake-kafka-connector.git
> $ cd snowflake-kafka-connector
> $ mvn clean verify -Daether.dependencyCollector.impl=bf {code}
>
> A related issue -
> [https://github.com/redhat-developer/vscode-java/issues/3085]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
