archiva-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Domsch (JIRA)" <>
Subject [jira] Commented: (MRM-727) Archiva does not download plugin artifacts
Date Tue, 04 Mar 2008 11:01:29 GMT


Christian Domsch commented on MRM-727:

I debugged through archiva and found out, that one reason for this bug, is that in DefaultRepositoryProxyConnectors
in line 405 the filename for the local repo file gets renamed from maven-metadata.xml to maven-metadata-central.xml.
This causes a problem later on, when this file is accessed because 1. the file never gets
found by maven and 2. if you try to access it directly ProxiedDavServer fails to recognize
it as a metadata file because the check in line 341 compares it to the string "maven-metadata.xml"
and fails.

> Archiva does not download plugin artifacts
> ------------------------------------------
>                 Key: MRM-727
>                 URL:
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: Ubuntu 7.10 x64, jdk1.6.0_04 x64, geronimo 2.0.2, maven 2.0.8 on
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>         Attachments: settings-wrong.xml
> When i have an initially blank local maven repo and for example start maven with "mvn
clean", no artifacts get downloaded. Maven is configured via the attached settings.xml. When
i monitor the tcp traffic, i see that the GET (in this case for the maven-metadata.xml for
maven-clean-plugin) request issued to archiva is the correct one. Archiva responses with a
> When I browse the repository file system on the server where archiva stores its files,
i see that a maven-metadata-central.xml was stored. the contents of this file are not correct,
> From trial and error I found out, that any request to a plugin related maven-metadata.xml
file will fail. If I try the same for a "normal" artifact maven-metadata.xml (like the one
for commons-lang) then archiva downloads the correct file.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message