[
https://issues.apache.org/jira/browse/MNG-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307591#comment-17307591
]
Herve Boutemy commented on MNG-7128:
------------------------------------
yes, not so easy
because the "blocked mirror" control currently only happens in Maven Resolver
when transitives are resolved (the location where it's not obvious to fix and
even detect, then our initial focus when working on the feature)
it does not (yet) happen in Maven when calling Maven Resolver, with initial
list of repositories from build/reactor POM extracted from effective POM and
mirror already injected: this happens in DefaultModelBuilder
[https://maven.apache.org/ref/3.6.3/maven-model-builder/xref/org/apache/maven/model/building/DefaultModelBuilder.html#L651]
and LifecycleDependencyResolver
it's in good part what makes repositories defined in reactor/build POMs
different from repositories defined in dependencies POMs, with different order
and different download cycle
> improve error message when blocked repository defined in build POM
> ------------------------------------------------------------------
>
> Key: MNG-7128
> URL: https://issues.apache.org/jira/browse/MNG-7128
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.8.0
> Reporter: Herve Boutemy
> Priority: Major
>
> MRESOLVER-166 brings an enhanced message when the blocked repository comes
> from a dependency
> But when blocked repository is defined in build pom.xml, there is not
> dedidated message: user has to guess that "Downloading from
> maven-default-http-blocker: http://0.0.0.0/..." comes from such a case
--
This message was sent by Atlassian Jira
(v8.3.4#803005)