The maven snapshot removal task is doing more work than expected. Expected that it would look at the snapshots in the snapshot repo and then check whether those exist in release repos. Instead it seems to be looking in other repos and checking whether those components exist in the snapshot repo.
Steps to reproduce:
Create a new maven snapshot repo and add one 0.0.1-SNAPSHOT version of a component.
Configure the snapshot removal task with minimum snapshot count 1 and remove if released enabled with a grace period 1 day.
Run the task with debug logging enabled.
The snapshot would not be removed since it was just added, and there would be very little activity recorded in the log since there is just one snapshot in the repo and nothing to clean up.
A whole bunch of debug log messages were recorded looking for components that do not exist in the snapshot repository. From the logs it looks like the task is iterating over other repositories, such as the central proxy, and checking whether those components exist in the snapshot repo.
Example log entry:
Searching for nexus-buildsupport only exists in Central proxy repo.