[
https://issues.apache.org/jira/browse/MRESOLVER-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818966#comment-17818966
]
ASF GitHub Bot commented on MRESOLVER-496:
------------------------------------------
cstamas commented on PR #434:
URL: https://github.com/apache/maven-resolver/pull/434#issuecomment-1954925113
Just FTR, original of this code still exists in (now deprecated) class:
https://github.com/apache/maven-resolver/blob/2f94fd7a1f42c26213a480b9a2dc65bca7f8df53/maven-resolver-util/src/main/java/org/eclipse/aether/util/ChecksumUtils.java#L58-L59
> Move Resolver off java.io.File to NIO2 Paths
> --------------------------------------------
>
> Key: MRESOLVER-496
> URL: https://issues.apache.org/jira/browse/MRESOLVER-496
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0-alpha-8, 2.0.0
>
>
> Internally, stop using java.io.File and use NIO2 Paths instead. From outside,
> this should not make a lot of difference.
> But, as a consequence: if Resolver used on FileSystem like Google JIMFS,
> whatever code touches File method (that will do Path.toFile() under the
> hood), it will explode. Hence, we need to make sure this call never happens
> internally, and leave it to consumer projects. Resolver alone should never
> invoke it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
