[
https://issues.apache.org/jira/browse/MRESOLVER-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738868#comment-17738868
]
ASF GitHub Bot commented on MRESOLVER-376:
------------------------------------------
caiwei-ebay2 commented on PR #309:
URL: https://github.com/apache/maven-resolver/pull/309#issuecomment-1614097696
@cstamas
A few questions.
BF patch do considers relocated artifact but does not work for this case,
May I know what's the special thing of this relocation artifact?
From my original implementation, it is like this:
A1 will be relocates to A2, so first we resolve A1, we cache A2's descriptor
with A2's key, next resolve A2, A2 is already there.
This is different with the behavior as you observed.
"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"
Let me try reproduce the issue.
> 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)
