Hi all,

over the last few days we experienced rather slow repository scanning
(mainly purge was slow), so we investigated the issue.

What we found out is, that we had a few projects which accidentally
deployed the same classifier with two different file extensions (in that
case -javadoc.zip and -javadoc.jar).

It seems that the purge deleted the snapshot -javadoc.jar but left the
-javadoc.zip and we ended up with several thousand files in one
directory which slowed down the repository scan to take ages.

The question is: Can or should Archiva either
a) refuse deployment if the same classifier is deployed twice with a
different extension
or
b) the purge be enhanced to delete all extensions of a given classifier?

Greetings
-Sascha-

Reply via email to