[ 
https://issues.apache.org/jira/browse/MRESOLVER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693282#comment-17693282
 ] 

ASF GitHub Bot commented on MRESOLVER-329:
------------------------------------------

michael-o commented on PR #257:
URL: https://github.com/apache/maven-resolver/pull/257#issuecomment-1444066052

   I'd like better understand whether the usecases file w/o temp files. I want 
to exclude our locks to be faulty here.




> 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
>             Fix For: 1.9.6
>
>
> 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)

Reply via email to