You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/04/03 21:33:00 UTC
[jira] [Closed] (MNG-6613) Mirror matching ignores closest/nearest
definition
[ https://issues.apache.org/jira/browse/MNG-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MNG-6613.
-------------------------------
Resolution: Fixed
Fixed with 76c80f1dfeaca8d14a09e80193e1c45bfb42f777 in integration tests.
> 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, Integration Tests
> 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)