[
https://jira.codehaus.org/browse/MRM-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326903#comment-326903
]
David Matejcek commented on MRM-1477:
-------------------------------------
I have Archiva 1.3.5 and uploaded an artifact that already existed with an
older version. Metadata file then was left unchanged, so maven build failed.
Then I opened the repository page and checked the "Process All Artifacts"
checkbox and sumbitted the button "Scan Repository Now".
Then the metadata file has been changed and even a maven build was successful
(with -U).
But maybe it should be better to run the scan right after the upload ...
> maven-metadata.xml is not generated or updated
> -----------------------------------------------
>
> Key: MRM-1477
> URL: https://jira.codehaus.org/browse/MRM-1477
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3.4
> Environment: Windows XP
> Reporter: notzippy
> Fix For: 1.4.1
>
>
> I just upgraded from 1.3.1 to 1.3.4 when this problem started to occur.
> Before archiva would generate the maven-metadata.xml through the web
> interface and using the ant task from ivy. Now neither generate the
> maven-metadata.xml file.
> I also tried the repository scanner would to create the maven-metadata.xml,
> but it does not either (metadata-updater is enabled).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
