[ 
http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter updated MRM-727:
-----------------------------

    Fix Version/s:     (was: 1.0.x)
                   1.0.2

> Archiva does not download plugin artifacts in Geronimo
> ------------------------------------------------------
>
>                 Key: MRM-727
>                 URL: http://jira.codehaus.org/browse/MRM-727
>             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 client
>            Reporter: Christian Domsch
>            Assignee: Maria Odea Ching
>             Fix For: 1.0.2
>
>         Attachments: maven-resources-plugin-maven-metadata-central.xml, 
> MRM-727-build-stack-trace.txt, 
> MRM-727-geronimo-tomcat-log-0.0.0.0_access_log.2008-03-10.txt, 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 404.
> 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, though.
> 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: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to