[ 
http://jira.codehaus.org/browse/MRM-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130206#action_130206
 ] 

Jason Chaffee commented on MRM-772:
-----------------------------------

If I "touch" the artifacts that remain on the file system after deleting, then 
it will update the metadata file correctly.

However, it would be better if it updates this regardless of the other 
artifacts being touched because we would prefer that the file system timestamp 
be the same as the actual deploy timestamp and touching would change this and 
make it a little more confusing for someone looking at the file system.

> metatadata-updater should update all sections of the metadata file, if there 
> is something not correct
> -----------------------------------------------------------------------------------------------------
>
>                 Key: MRM-772
>                 URL: http://jira.codehaus.org/browse/MRM-772
>             Project: Archiva
>          Issue Type: Improvement
>          Components: repository scanning
>    Affects Versions: 1.0.2
>            Reporter: Jason Chaffee
>            Priority: Critical
>
> According to the documentation the metadata-updater will do the
> following: 
> metadata-updater - Updates artifact metadata files depending on the content 
> of the repository. 
> I have been testing this by deploying several artifacts to the repository and 
> getting a specific timestamp and build number in the maven-metatadata.xml 
> file.  Next, I delete the latest (snapshot) build from the repo, including 
> checksums.  I run the repository scanner and the database-updater and this 
> file is never fixed based on the actual contents of the file system.  Archive 
> updates it internal metadata, but not maven's metadata and thus maven fails 
> to download the artifact. 
> From Brett:
> I think at present the updater corrects the <versions> flag, but not the 
> snapshot information (it also doesn't correct the plugin group metadata).

-- 
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