[jira] [Commented] (MRESOLVER-605) FileTransporter should offer symlink, hardlink ops aside of existing copy

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

cstamas merged PR #578:
URL: https://github.com/apache/maven-resolver/pull/578




> FileTransporter should offer symlink, hardlink ops aside of existing copy
> -------------------------------------------------------------------------
>
>                 Key: MRESOLVER-605
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-605
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 2.0.2
>
>
> FileTransport is a "remote repository" transport that is using FS, hence, is most probably "local" to Resolver process (does not have to be, ie. use of NFS mount or alike).
> Hence, FileTransport should offer some means to not copy but link the files. FileTranport is usually used in tests and alike, so doing this would lessen disk store usage and even execution times.
> Still, given FileTranport is "remote" transport, checksumming must happen, hence file being transported must be read (so gain is not "just link it", is way less).
> Big fat note: this change will cause that symlinks may land in local repository. This change does NOT enforce rest of Maven plugins knows how to handle them, is out of scope.
> Other alternative for "local test setups" is ChainedLocalRepository.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)