https://defect.opensolaris.org/bz/show_bug.cgi?id=16913
Summary: Opengrok fails to use JDBC cache if -R option is
specified
Classification: Development
Product: opengrok
Version: unspecified
Platform: ANY/Generic
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: indexer
AssignedTo: [email protected]
ReportedBy: [email protected]
CC: [email protected]
--- Comment #0 from Martin Walsh <[email protected]> 2010-08-25 09:31:43
UTC ---
When indexing source code using the -D option to specify history cache uses a
database, if the -R option is specified to read an existing configuration, the
History is always generated to file not to database.
This is because the -R option is handled first, reading in any existing
configuration via the RuntimeEnvironment. This in turn initialises the
HistoryGuru, which checks the config to see which type of cache to use. As the
-D option has not been handled yet, it uses files. This is then set
permanently for the life of the application, as HistoryGuru is a singleton. So
when indexing commences, even though the config is correct, the HistoryGuru
used is still setup using files, instead of the database.
--
Configure bugmail: https://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
opengrok-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opengrok-dev
