Hi, Knut: thanks, that explains it!
The index creation logs say 258 11:35:20,583 org.opensolaris.opengrok.index.Indexer INFO: Done... 259 11:35:20,584 org.opensolaris.opengrok.index.Indexer INFO: Generating history cache for all repositories ... 301 11:35:20,626 org.opensolaris.opengrok INFO: Create historycache for /BUILD/spool/test/opengrok/src/HEAD (CVSRepository) 302 11:35:20,627 org.opensolaris.opengrok INFO: Creating historycache for /BUILD/spool/test/opengrok/src/HEAD took (1ms) 354 11:35:20,679 org.opensolaris.opengrok.index.Indexer INFO: Done... 355 11:35:20,680 org.opensolaris.opengrok.index.Indexer INFO: Starting indexing 611 11:35:20,936 org.opensolaris.opengrok INFO: Create historycache for /BUILD/spool/test/opengrok/src/HEAD (CVSRepository) 611 11:35:20,936 org.opensolaris.opengrok INFO: Creating historycache for /BUILD/spool/test/opengrok/src/HEAD took (0ms) 665 11:35:20,990 org.opensolaris.opengrok.index.IndexDatabase INFO: Counting files in /HEAD ... Which implies that the historycache *will* be used. Could the log messages display something like historycache not active for CVS repositories instead? Would make it a bit clearer :) Regards, Mark -----Message d'origine----- De : Knut Anders Hatlen [mailto:knut.hat...@oracle.com] Envoyé : mercredi 27 juin 2012 09:39 À : Clements Mark Cc : opengrok-discuss@opensolaris.org Objet : Re: javadb historycache not being used with CVS "Clements Mark" <cleme...@ofac.ch> writes: > Hi, > > We have been running opengrok to index source held in a CVS repository > for several years. I’ve noticed today that the derby historycache does > not appear to be being used. That's right. The Derby history cache is only used if the version control system has global revisions, not if it has per-file revisions (like CVS, RCS and SCCS). Viewing the history should still work, but the cache is bypassed. -- Knut Anders _______________________________________________ opengrok-discuss mailing list opengrok-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
