[
https://jira.codehaus.org/browse/MRM-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296156#comment-296156
]
Sascha Vogt commented on MRM-1622:
----------------------------------
Further debugging revealed:
# The purge consumer calls ManagedRepositoryContent.getRelatedArtifacts()
# The set returns only contains ArtifactReferences which only have a type, not
an extension
# The purge consumer converts the references back to actual files, where the
type gets translated to it's default extension
Now, as type "javadoc" always gets translated to .jar, -javadoc.zips will never
be purged.
So actually it has nothing to do, if an artifact is deployed twice with a
different extension - it just refers to the type / extension mapping (see
ArtifactExtensionMapping). If one uses one of the known types with a different
extension, then purge will never clean these up.
I propose raising the priority for that.
> Repository purge only purges one file extension per classifier
> --------------------------------------------------------------
>
> Key: MRM-1622
> URL: https://jira.codehaus.org/browse/MRM-1622
> Project: Archiva
> Issue Type: Improvement
> Components: repository scanning
> Affects Versions: 1.3.5
> Reporter: Sascha Vogt
> Priority: Minor
>
> In case a classifier gets deployed two times with a differnt file extension
> (e.g. -javadoc.jar and -javadoc.zip), repository purge only deletes one and
> leaves the other one. In case of lots of snapshot builds the directory fills
> up and slows down the repository scanning until it is stuck.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
