[
https://issues.apache.org/jira/browse/MRESOLVER-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780203#comment-17780203
]
Slawomir Jaranowski commented on MRESOLVER-392:
-----------------------------------------------
Installer are used in m-invoker-p - on each build we install all project
dependency in local mock repository.
So default policy with "warn" can introduce many logs in such task.
Maybe we need a "smart" checking in m-invoker-p ... I need check it - maybe it
is in place.
> Resolver installer should not be "smart" about installs
> -------------------------------------------------------
>
> Key: MRESOLVER-392
> URL: https://issues.apache.org/jira/browse/MRESOLVER-392
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> Seems in some cases (equality by timestamp and file size) DefaultInstaller
> will NOT install the requested file, and log this fact on DEBUG level.
> This is wrong: resolver should NOT be "smart" in this case. IMO, if "install
> request" flies it, resolver should install unconditionally.
> Or, maybe perform some more checks, and refuse install in case like:
> * release artifact that is already present in local repository?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
