[ 
https://issues.apache.org/jira/browse/MRESOLVER-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MRESOLVER-168:
------------------------------------
    Fix Version/s: 1.6.3

> add DEBUG message when downloading an artifact from repositories
> ----------------------------------------------------------------
>
>                 Key: MRESOLVER-168
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-168
>             Project: Maven Resolver
>          Issue Type: Improvement
>          Components: Resolver
>    Affects Versions: 1.6.2
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>            Priority: Major
>             Fix For: 1.6.3, 1.7.0
>
>
> currently, when download artifacts, we have many DEBUG messages on low level 
> technical details
> {noformat}[DEBUG] Writing tracking file 
> /home/user/.m2/repository/org/apache/apache/23/apache-23.pom.lastUpdated
> [DEBUG] Using transporter WagonTransporter with priority -1.0 for 
> https://repo.maven.apache.org/maven2/
> [DEBUG] Using connector BasicRepositoryConnector with priority 0.0 for 
> https://repo.maven.apache.org/maven2/
> Downloading from central: 
> https://repo.maven.apache.org/maven2/org/apache/apache/23/apache-23.pom
> Downloaded from central: 
> https://repo.maven.apache.org/maven2/org/apache/apache/23/apache-23.pom (18 
> kB at 1.3 MB/s)
> [DEBUG] Writing tracking file 
> /home/user/.m2/repository/org/apache/apache/23/_remote.repositories
> [DEBUG] Writing tracking file 
> /home/user/.m2/repository/org/apache/apache/23/apache-23.pom.lastUpdated
> {noformat}
> adding before a message about what artifact is being resolver, and in which 
> repositories (with explicit order that will be used) would be a lot more 
> useful:
> {noformat}[DEBUG] Resolving artifact org.apache:apache:pom:23 from [central 
> (https://repo.maven.apache.org/maven2/, default, releases), apache.snapshots 
> (https://repository.apache.org/snapshots, default, snapshots)]{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to