[jira] [Commented] (MNG-6857) When a repository we are referring to , in pom.xml has been made down or shut down . The maven is not handling it appropriately

["Elliotte Rusty Harold (Jira)" <ji...@apache.org>]

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

Elliotte Rusty Harold commented on MNG-6857:
--------------------------------------------

If Maven can't handle a valid 301/302, that's a serious bug.

 

However I disagree that maven should go to the next available repository listed in pom.xml to check for this jar. This is contrary to the HTTP spec. HTTP requires that maven find the new repo location at the URL advertised in the 3xx response.

 

If and only if that repo is unreachable or blocked in some way, then Maven should treat that the same is it would if the original repo had given the same response.

 

 

> 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)