Issue Details (XML | Word | Printable)

Key: MRM-537
Type: Bug Bug
Status: Closed Closed
Resolution: Duplicate
Priority: Major Major
Assignee: Unassigned
Reporter: Graeme Steyn
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Archiva

Deletion of artifacts from Archiva Managed Repositories not being detected

Created: 10/Oct/07 11:21 PM   Updated: 10/Oct/07 11:37 PM   Resolved: 10/Oct/07 11:30 PM
Component/s: repository scanning
Affects Version/s: 1.0-beta-2
Fix Version/s: None

Time Tracking:
Not Specified

Environment: Windows XP SP2 and Solaris - Default install run via plexus.
Issue Links:
Duplicate
 


 Description  « Hide

1. Manually delete a tree of artifacts from the managed repository being used for testing, e.g. delete com.* tree.
2. In administration console select Repositories.
3. Click "Scan Repository Now" for test repository where artifacts were deleted.
4. Database > Update Database Now.
5. Browse.

The index information has not been updated and the entire tree just deleted can still be browsed. Similarly, if you update a single POM for an artifact and its MD5/SHA files, then refresh, the changes are not reflected in the browser information for the POM



Wendy Smoak added a comment - 10/Oct/07 11:37 PM

The deletion issue is already open as MRM-37, so I marked this as a duplicate based on the summary.

I've also experienced the issue with POM changes not being picked up. You can open a separate issue for that, if there isn't one already.