Gwyn Connor created MRM-1899:
--------------------------------

             Summary: Artifact checksums not always generated for remote proxy
                 Key: MRM-1899
                 URL: https://issues.apache.org/jira/browse/MRM-1899
             Project: Archiva
          Issue Type: Bug
          Components: remote proxy
    Affects Versions: 2.2.0
            Reporter: Gwyn Connor


Archiva sometimes does not create checksums (and metadata) for proxied POM-only 
artifacts from remote repository when they are downloaded for the first time. 
It downloads the .pom and writes the pom's content to .sha1 and .md5 files.

Any tool using the checksum files will fail, because they do not contain 
checksums but are corrupt (i. e. they contain the XML content from the POM).

Running a directory scan on the managed repository fixes the checksum files and 
creates the metadata.

I can reproduce this behaviour everytime on an empty repository, when I try to 
download artifacts from Maven Central proxy with Gradle. I've attached the 
Archiva logs (with INFO level enabled). You can see that checksums for 
org/apache/apache/13/apache-13.pom are only created after manually starting a 
directory scan.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to