[
https://issues.apache.org/jira/browse/MNG-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309825#comment-17309825
]
Herve Boutemy edited comment on MNG-7128 at 3/27/21, 12:46 AM:
---------------------------------------------------------------
yes: I intend to create a core IT before merging to master, because that's one
key part missing in my current work (I had to prioritize), and MNG-7118 feature
is sufficiently important to make sure we don't regress over Maven releases
as we don't have much habit on parallel branch maintenance, in terms of Jira,
yes, we're currently in a half-baked situation (this Jira issue is closed to
release Maven 3.8.1, but the integration into master branch is not done)
this proves me if I needed it that I don't want to maintain multiple branches
in parallel in the long term...
was (Author: hboutemy):
yes: I intend to create a core IT before merging to master, because that's one
key part missing in my current work (I had to prioritize), and MNG-7118 feature
is sufficiently important to make sure we don't regress over Maven releases
> 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: Bug
> Affects Versions: 3.8.0
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 3.8.1
>
>
> 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
>
> The download is not blocked as expected before even trying to download, but
> the download fails because this is the intent of the chosen
> [http://0.0.0.0|http://0.0.0.0/] url...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)