You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Wendy Smoak (JIRA)" <ji...@codehaus.org> on 2009/09/04 18:00:31 UTC

[jira] Commented: (MRM-1246) MetadataUpdaterConsumer didn't run during a repository scan after deleting a version of an artifact.

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

Wendy Smoak commented on MRM-1246:
----------------------------------

When this happens, I notice that the deleted artifacts are still visible in search/browse, meaning they are still in the database.

I think it's less that the metadata update consumer didn't run, and more that Archiva didn't "see" the deletion at all, so there were no events for the various consumers to process.


> MetadataUpdaterConsumer didn't run during a repository scan after deleting a version of an artifact.
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MRM-1246
>                 URL: http://jira.codehaus.org/browse/MRM-1246
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Gwen Harold Autencio
>
> Steps to replicate
> 1. Deploy several test snapshots with
> mvn deploy:deploy-file -Dfile=test.jar -DgroupId=com.example.test -DartifactId=test -Dversion=2.0-SNAPSHOT -Durl=file:///home/gwen/repository/snapshots -Dpackaging=jar
> and repeat several times for version 1.0, 1.1 (results in timestamped snapshots).
> 2. Open /home/gwen/repository/snapshots/com/example/test/test/maven-metadata.xml. All version can be seen.
> 3. Scan the repository and update the database. Confirm that the artifacts are all visible through the browse url.
> 4. Delete the com/example/test/test/1.1-SNAPSHOT directory from the repository
> 5. Click "Scan repository now" for the Snapshots repository and wait for the scan to finish
> 6. View the metadata file again.
> Expected result: version 1.1-SNAPSHOT is not in the maven-metadata.xml file
> Actual result: the metadata file still contains version 1.1-SNAPSHOT

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