archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deng Ching <och...@apache.org>
Subject Re: work left to do on MRM-1025 branch
Date Thu, 18 Feb 2010 14:59:25 GMT
Hi Brett,

I'm getting test failures in MRM-1025 branch in
archiva-modules/plugins/maven2-repository module. From the surefire-reports
of Maven2RepositoryMetadataResolverTest, it looks like an ordering problem
in the results being compared in one of the assertions..

-Deng

On Thu, Feb 18, 2010 at 10:47 PM, Deng Ching <oching@apache.org> wrote:

> On Wed, Feb 17, 2010 at 6:44 AM, Brett Porter <brett@apache.org> wrote:
>
>>
>> On 17/02/2010, at 3:28 AM, Deng Ching wrote:
>>
>> >
>> > In the Configuration section in
>> > http://archiva.apache.org/ref/1.4-SNAPSHOT/metadata-content-model.html, it
>> > was mentioned that the config should be shadowed to a file in the file
>> > system. Is this a one-to-one relationship (e.g. one repository == one
>> config
>> > file)?
>>
>> Not necessarily. I expect this would continue to use the same file as now,
>> but we can probably simplify the handling quite a bit.
>>
>>
> Ah, ok :) I thought it's going to be a different file from the archiva
> config.
>
>
>>  >>
>> >> * Deletion detection in scanning is still missing, though it would now
>> be
>> >> quite easy to add back, I didn't get around to it.
>> >>
>> >
>> > In trunk now and in the previous releases, new artifacts are detected
>> based
>> > on its modified date and the last repo scan.. I assume it's still the
>> same?
>>
>> Yes, no change to the scanning at present, the last repo scans are
>> recorded in the content repository. However, the deletion detection was in
>> the "database scanning" that is no longer present. While everything else in
>> there was migrated to a different solution, this needs to be added back to
>> go through the content repository and find stale nodes. The reason I didn't
>> do it yet was that I was considering whether to introduce this as a properly
>> scheduled, separate, service, or to just take the easier option for now and
>> tack it on to the end of the repository scan.
>>
>
> Makes sense..
>
> Thanks,
> Deng
>
>
>> >>
>> >> * While it should be very straightforward, we need to test some
>> scenarios
>> >> of upgrading from Archiva 1.3.
>> >>
>> >
>> > ..and also upgrading from the lower versions :)
>>
>> Good point!
>>
>> > I haven't finished reviewing everything and I'm pretty tired (brain
>> isn't
>> > working properly now) so I'll just continue looking over this tomorrow
>> :)
>>
>> Thanks!
>>
>> - Brett
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>>
>>
>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message