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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2
• Fix Version/s: 1.3
• Flags: Patch
• Assignee: Jevica Arianne B. Zurbano
• Reporter: Gwen Harold Autencio
• Created: 04/Sep/09 00:21
• Updated: 05/Apr/15 14:53
• Resolved: 02/Nov/09 20:42

Description

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

Issue Links

• is duplicated by: MRM-1326 delete artifact does not update metadata.xml