On Thu, Apr 22, 2010 at 10:15 AM, Gwen Harold Autencio < [email protected]> wrote:
> Sorry. The 3rd paragraph would be the action for MRM-1345. > > --- On Wed, 4/21/10, Gwen Harold Autencio <[email protected]> wrote: > > From: Gwen Harold Autencio <[email protected]> > Subject: MRM-1345 > To: [email protected] > Date: Wednesday, April 21, 2010, 8:15 PM > > Hi, > > I have investigated on MRM-1345. > I used the archiva trunk and changed the version of nexus-indexer to the > latest release which is 2.0.5. > > The > difference that I found bet 2.0.0 and 2.0.5 is that2 IndexCreator were > added in 2.0.1 (MavenPluginArtifactInfoIndexCreator and > MavenArchetypeArtifactInfoIndexCreator). And the static field that lists all > the IndexCreator in NexusIndexer has been removed that. > > Create the list in archiva that contains all the IndexCreator. > Unit tests of archiva-index and archiva-indexer-scheduling needs to be > adjusted since it will fail on the new IndexCreator( > MavenArchetypeArtifactInfoIndexCreator ). > > > This > is what I have seen so far. Can I ask enlightenment about the " > addition of features such as creating incremental indexes" ? > This feature refers to https://issues.sonatype.org/browse/NEXUS-1041 and it is also worth reading http://www.sonatype.com/people/2009/05/nexus-indexer-20-incremental-downloading/to better understand it. For the implementation of this in Archiva, I think this can either be attached/added to the existing indexer consumer or add a new consumer that specifically creates the incremental index. I prefer the latter so that the user can control whether to turn it on and off, separate from the generation of the full index. BTW, you can create a separate sub-task for this to keep it separate from the other changes related to the upgrade :) > And any other things that needs to be done for MRM-1345? > > Any thoughts or comment would surely help. > > Thanks, > Gwen > > Thanks, Deng
