[
http://jira.codehaus.org/browse/MRM-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196225#action_196225
]
Yanke commented on MRM-1246:
----------------------------
in case somebody searches for a workaround:
we had the same problem but with Archiva 1.2.2 we have been able to remove it
using the "Delete Artifact" menu.
Not as efficient as automatic updating the DB, but at least the wrong version
was gone.
I haven't tested if "Delete Artifact" would delete an artifact from DB also if
it does not exist on the repository (I have manually added it before deleting)
> 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
> Assignee: Jevica Arianne B. Zurbano
> Fix For: 1.2.3
>
> Attachments: MRM-1246.patch, updated-MRM-1246.patch
>
>
> 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
