[
https://issues.apache.org/jira/browse/MNG-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615298#comment-16615298
]
Michael Osipov commented on MNG-6477:
-------------------------------------
Please show a log and command line depicting the issue. What you are requesting
what is already implemented.
> Check dependency is already downloaded and up-to-date locally, instead of
> downloading each time on mvn update
> -------------------------------------------------------------------------------------------------------------
>
> Key: MNG-6477
> URL: https://issues.apache.org/jira/browse/MNG-6477
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
> Affects Versions: 3.5.0
> Reporter: chamarthi venkata hrudayanath
> Priority: Critical
>
> Check whether the dependency is already downloaded in local system and is
> up-to-date with latest one before downloading a new one from mvn repository
> each time when doing a maven update. Thereby it improves the performance and
> saves lot of data for all using maven project.
> Approaches that can be used:
> 1) when requested for a maven update, get the individual hash of dependencies
> already downloaded locally and sent them to mvn repo server. then mvn server
> should figure out the updated dependencies and new ones based on hashes. then
> it must download only those which are updated and new ones.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
