[
https://issues.apache.org/jira/browse/MNG-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074668#comment-17074668
]
Michael Osipov edited comment on MNG-6613 at 4/3/20, 3:34 PM:
--------------------------------------------------------------
Thinking more about this, should there be a circuit breaker? You cannot
(should) not have a mirror of a mirror? Does this make sense at all? Is a
mirror considered as a repo too?
[~rfscholte], WDYT?
was (Author: michael-o):
Thinking more about this, should there be a circuit breaker? You cannot
(should) not have a mirror of a mirror? Does this make sense at all? Is a
mirror considered as a repo too?
> Mirror matching ignores closest/nearest definition
> --------------------------------------------------
>
> Key: MNG-6613
> URL: https://issues.apache.org/jira/browse/MNG-6613
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.5.4, 3.6.1
> Environment: Java 8u202, Java11u2
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Critical
> Attachments: log.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ran our IT suite in a locked down environment at work, w/o direct internet
> access. IT {{mng3461MirrorMatching(itNonGreedyWildcard)}} blocks forever
> because the mirror exclude does not work: {{*,!maven-core-it}}.
> It still tries to download via mirror instead of ignoring it. See attached
> log file. Even switching {{!maven-core-it,*}} makes no difference.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
