[
https://issues.apache.org/jira/browse/MRESOLVER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688620#comment-17688620
]
ASF GitHub Bot commented on MRESOLVER-320:
------------------------------------------
cstamas opened a new pull request, #243:
URL: https://github.com/apache/maven-resolver/pull/243
There was some information lost on the way how we got to current master:
artifact and dependency was ALWAYS weak, and the "cause" commit
6dda69980cf4c13228a4f6561bfa0d8384a0be68 modified ONLY the descriptor pool (was
hard by mistake, made it weak). This also explain why we saw with yourkit
excess Xpp3 and model building requests as well (as starting with 1.8.x
descriptors/POMs were GCed, while before they were not).
This PR essentially returns the state of affairs to pre 1.8.x resolver state
re data pools, but also adds ability to "tune" each three of them separately.
---
https://issues.apache.org/jira/browse/MRESOLVER-320
> Investigate slower resolving speeds as reported by users
> --------------------------------------------------------
>
> Key: MRESOLVER-320
> URL: https://issues.apache.org/jira/browse/MRESOLVER-320
> Project: Maven Resolver
> Issue Type: Task
> Affects Versions: 1.9.4
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.5
>
>
> Users on ML reported "slowness" that MAY be caused by a change added in 1.9.0
> version of resolver MRESOLVER-250.
> [https://lists.apache.org/thread/r9p236z8kvqqk7ykvkgmc5wgps6n1hkf]
> [https://github.com/apache/maven-resolver/pull/166#issuecomment-1413808333]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
