You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/04/01 06:09:00 UTC

[jira] [Commented] (MNG-6613) Mirror matching ignores closest/nearest definition

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

Hudson commented on MNG-6613:
-----------------------------

Build unstable in Jenkins: Maven TLP » maven » MNG-6512-build-11 #17

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6512-build-11/17/

> 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
>            Priority: Critical
>         Attachments: log.txt
>
>
> 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
(v7.6.3#76005)