ore a final (non-beta, non-RC,
> release)
>
> Now is the perfect time to correct this.
> Lets do it now.
> Lets put it up for a vote now.
>
>>
>> Let's just define what the acceptable extension points for Archiva 1.0
>> are (probably consumers, so maybe you've found the one example where
>> it might be difficult!), document them, and commit to maintaining them
>> and move forward in that way.
>>
>> - Brett
>
> --
> - Joakim Erdfelt
> [EMAIL PROTECTED]
> Open Source Software (OSS) Developer
>
>
>
--
View this message in context:
http://www.nabble.com/Archiva-Consumers-question-tf4637899.html#a13277036
Sent from the archiva-dev mailing list archive at Nabble.com.
On 10/17/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
> Everything in the UI uses the database.
> A full scan from disk to database take *FAR* too long.
>
> This was setup as a tiered effort.
> First step. get the real, valid, useful content off of disk and into the
> database into a usable form.
Brett Porter wrote:
Well, since you asked :)
On 17/10/2007, at 2:10 PM, Joakim Erdfelt 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 con
Everything in the UI uses the database.
A full scan from disk to database take *FAR* too long.
This was setup as a tiered effort.
First step. get the real, valid, useful content off of disk and into the
database into a usable form.
Second step. expand the data in the database fully.
The first
