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

ASF GitHub Bot commented on MNG-5457:
-------------------------------------

Github user michael-o commented on the issue:

    https://github.com/apache/maven/pull/87
  
    This is the snapshot: `Downloading from central: 
https://repository.apache.org/snapshots/org/apache/maven/maven-embedder/3.4.0-SNAPSHOT/maven-embedder-3.4.0-20160712.211951-154.pom`
    
    Unfortunately, the mediated repo is only known to Aether. I have to fix 
this issue long time ago but was stuck at the same point. I think it won't work 
without an Aether fix.


> show repository id when downloading
> -----------------------------------
>
>                 Key: MNG-5457
>                 URL: https://issues.apache.org/jira/browse/MNG-5457
>             Project: Maven
>          Issue Type: Improvement
>          Components: General
>    Affects Versions: 3.0.5
>            Reporter: Hervé Boutemy
>             Fix For: 3.x / Backlog
>
>         Attachments: 2016-05-18_204749.png
>
>
> actually, the log only show the url being downloaded:
> {noformat}Downloading: 
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded: 
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
>  (9 KB at 98.7 KB/sec){noformat}
> nothing is told about the repository id.
> But as shown in MNG-5181, repository id is an important information since it 
> is stored in local repository to limit artifact scope: it would be useful 
> IMHO to display the id in the output, like 
> {noformat}Downloading from central: 
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded from central: 
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
>  (9 KB at 98.7 KB/sec){noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to