[
https://issues.apache.org/jira/browse/MNG-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074864#comment-17074864
]
Michael Osipov commented on MNG-6613:
-------------------------------------
My initial description is wrong because I have analyzed the issue now properly.
While our network has changed and surprisingly now works w/o a proxy, you can
still setp an IP address which does not exist, e.g,, {{192.168.0.1}} and it
will block. On Windows, the block is released quickly, on my corporate server
with FreeBSD it takes as long as the Wagon read timeout of 180 s. Will work on
a better test.
> 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)
