On 10/16/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
> ArchivaArtifactConsumer is an abstract-dealing-with-artifacts consumer.
> RepositoryContentConsumer is for files.
>
> A file that isn't an artifact can be *.xml, *.sha1, *.md5,
> maven-metadata.xml, bad content, poorly named content, etc.
>
> Would it be better to state the phase/scan instead?
>
> RepositoryContentConsumer becomes -> RepositoryScanConsumer
> ArchivaArtifactConsumer becomes -> DatabaseScanConsumer

All artifacts _are_ repository content, are they not?  And even after
the renaming... it can't be in the database unless it's in the
repository.

I understand scanning the filesystem to update the database.  But when
and why do you "scan" the database?

-- 
Wendy

Reply via email to