[
https://issues.apache.org/jira/browse/MNG-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074805#comment-17074805
]
Michael Osipov commented on MNG-6613:
-------------------------------------
So here it is:
No mirrors:
{noformat}
[DEBUG] Repositories (dependencies): [central (file:target/null, default,
releases), maven-core-it
(file:///D:/Entwicklung/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3461/test-3/repo,
default, releases)]
[DEBUG] Repositories (plugins) : [central (file:target/null, default,
releases+snapshots)]
{noformat}
Mirror: central
{noformat}
[DEBUG] Using mirror central (http://maven.apache.org/null) for central
(file:target/null).
...
[DEBUG] Repositories (dependencies): [central (http://maven.apache.org/null,
default, releases), maven-core-it
(file:///D:/Entwicklung/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-3461/test-3/repo,
default, releases)]
[DEBUG] Repositories (plugins) : [central (http://maven.apache.org/null,
default, releases+snapshots)]
{noformat}
Mirror: centraal
{noformat}
[DEBUG] Using mirror centraal (http://maven.apache.org/null) for central
(file:target/null).
...
Exceptions that files are not found
{noformat}
Why the failure? The problem is actually not the the test per-se and not the
outbound access. Reviewing MNG-3461 and as mentioned by Robert in the mini
guide, {{*}} matches all repos, even local ones as you can see for both
{{central}} and {{centraal}} (the Dutch version).
Now the problems:
* Test should not rely on outbound access to mute a non-existing local repo
with another repo non-existing repo. This could be simply done by another local
non-existing local repo.
* The mirror is called {{central}} which is not a problem. Why does not
{{centraal}} fail? {{central}} implicitly relies on the fact that
{{_remote.properties}} will contain {{${filename}>central=}} and central has
been used previously to download all artifacts. We modify with
{{maven.it.central}} and Bootstrap for that.
Now what I need to figure out what artifacts from pulled from non-existing
mirror and why they are not pulled from {{maven-core-it}}.
> 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)
