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
