You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/03/02 09:16:00 UTC
[jira] [Commented] (MRESOLVER-329) Make IO in DefaultTrackingFileManager more robust
[ https://issues.apache.org/jira/browse/MRESOLVER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695574#comment-17695574 ]
Tamas Cservenak commented on MRESOLVER-329:
-------------------------------------------
Not for 1.9.6, we need deeper analysis.
> Make IO in DefaultTrackingFileManager more robust
> -------------------------------------------------
>
> Key: MRESOLVER-329
> URL: https://issues.apache.org/jira/browse/MRESOLVER-329
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
>
> There are couple of spots where implementation naively assumes is alone running process on this world. Several user reports suggests this is not the case, like MRESOLVER-325 or MNG-7705. Fix these spots.
> Still, something is fishy, as it seems these files (all that are handled by DefaultTrackingFileManager) are not subject to locking? This needs investigation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)