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 Wed, 05 Mar 2008 23:41:28 GMT


Christian Domsch commented on MRM-727:

As far as I found out, part of the problem seems to be a classloading issue with geronimo.
I found out, that when the DefaultRepositoryProxyConnector finished with downloading the maven-metadata-central.xml,
it tries to merge it with a possible existing maven-metadata.xml. In this process, the previously
downloaded xml is read with a RepositoryMetadataReader, that uses dom4j internally with xpath
expressions. This process throws a NoDefClassFoundError while it tries to load org.dom4j.Element.
By googling this issue, I found this link:

I have no clue, what the real problem is in detail, nor how to solve it.

> 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: MRM727.diff, 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