[
https://issues.apache.org/jira/browse/MRESOLVER-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-496:
--------------------------------------
Description:
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.
> 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
> 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)
