[
https://issues.apache.org/jira/browse/MNG-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045841#comment-17045841
]
Michael Osipov edited comment on MNG-6857 at 2/26/20 7:47 PM:
--------------------------------------------------------------
Btw, the status code is not available in the high-level API because it is
transport-agnostic.
was (Author: michael-o):
Btw, the status code is not availabe in the highlevel API because it is
transport-agnostic.
> When a repository we are referring to , in pom.xml has been made down or shut
> down . The maven is not handling it appropriately
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-6857
> URL: https://issues.apache.org/jira/browse/MNG-6857
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.6.3
> Reporter: Devendra Tummala
> Priority: Major
> Labels: patch
> Fix For: waiting-for-feedback, wontfix-candidate
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I am working in Maven-Spring Boot Projects .
> I have a list of repositories listed down in my pom.xml and among those one
> is down/moved permanently(302 /301 status), then Maven is unable to handle it
> and downloading some corrupted jars from no where and when we try to "mvn
> install" ,it states error like "error in opening zip file" for that jar .
>
> Steps How we resolved that issue--
> 1.Commented out that repository in pom.xml
> 2.Removed that corrupted jar from local repository.
> 3.mvn -U clean install
>
> How we are expecting it to be resolved ::
> # If the repository throws 301/302 , the maven should go to the next
> available repository listed in pom.xml and should check for this jar .
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
