You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Stefanescu (JIRA)" <ji...@codehaus.org> on 2008/10/16 13:34:19 UTC

[jira] Created: (MNG-3794) Improve error logging when downloading depedencies

Improve error logging when downloading depedencies
--------------------------------------------------

                 Key: MNG-3794
                 URL: http://jira.codehaus.org/browse/MNG-3794
             Project: Maven 2
          Issue Type: Improvement
          Components: Logging
    Affects Versions: 2.0.8
            Reporter: Christian Stefanescu


When resolving dependencies (downloading pom.xml or jar files), the logging output does not offer any information as to WHY the respective file was not downloaded. Consider the following output (snipped from a standard "mvn install" run):

{quote}
Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
Downloading: http://mavenproxy/repository/unavailables/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
Downloading: http://mavenproxy/repository/inHouse//javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
Downloading: http://mavenproxy/repository/unavailables/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
Downloading: http://mavenproxy/repository/inHouse//javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
Downloading: http://download.java.net/maven/1//javax.xml.ws/jars/jaxws-api-2.1-1.jar
Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
{quote}

As you can see, a maven proxy is queried, and then re-checked, but no clear statement is made as to WHY this happens (could be connection problems, not found - 404, not authenticated - 401).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MNG-3794) Improve error logging when downloading depedencies

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3794:
------------------------------

    Fix Version/s: 2.1.0-M3

> Improve error logging when downloading depedencies
> --------------------------------------------------
>
>                 Key: MNG-3794
>                 URL: http://jira.codehaus.org/browse/MNG-3794
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Logging
>    Affects Versions: 2.0.8
>            Reporter: Christian Stefanescu
>             Fix For: 2.1.0-M3
>
>
> When resolving dependencies (downloading pom.xml or jar files), the logging output does not offer any information as to WHY the respective file was not downloaded. Consider the following output (snipped from a standard "mvn install" run):
> {quote}
> Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
> Downloading: http://mavenproxy/repository/unavailables/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
> Downloading: http://mavenproxy/repository/inHouse//javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
> Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
> Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
> Downloading: http://mavenproxy/repository/unavailables/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
> Downloading: http://mavenproxy/repository/inHouse//javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
> Downloading: http://download.java.net/maven/1//javax.xml.ws/jars/jaxws-api-2.1-1.jar
> Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
> {quote}
> As you can see, a maven proxy is queried, and then re-checked, but no clear statement is made as to WHY this happens (could be connection problems, not found - 404, not authenticated - 401).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (MNG-3794) Improve error logging when downloading depedencies

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MNG-3794.
-----------------------------

         Assignee: Brett Porter
       Resolution: Fixed
    Fix Version/s: 2.0.11

> Improve error logging when downloading depedencies
> --------------------------------------------------
>
>                 Key: MNG-3794
>                 URL: http://jira.codehaus.org/browse/MNG-3794
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Logging
>    Affects Versions: 2.0.8
>            Reporter: Christian Stefanescu
>            Assignee: Brett Porter
>             Fix For: 2.0.11, 2.1.0
>
>
> When resolving dependencies (downloading pom.xml or jar files), the logging output does not offer any information as to WHY the respective file was not downloaded. Consider the following output (snipped from a standard "mvn install" run):
> {quote}
> Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
> Downloading: http://mavenproxy/repository/unavailables/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
> Downloading: http://mavenproxy/repository/inHouse//javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
> Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.pom
> Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
> Downloading: http://mavenproxy/repository/unavailables/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
> Downloading: http://mavenproxy/repository/inHouse//javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
> Downloading: http://download.java.net/maven/1//javax.xml.ws/jars/jaxws-api-2.1-1.jar
> Downloading: http://mavenproxy/repository/proxy/javax/xml/ws/jaxws-api/2.1-1/jaxws-api-2.1-1.jar
> {quote}
> As you can see, a maven proxy is queried, and then re-checked, but no clear statement is made as to WHY this happens (could be connection problems, not found - 404, not authenticated - 401).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira