avoid global isHistoryEnabled() checks in favor of per repository check #4746
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change allows for real per project history override.
Tested with indexer running with:
where the contents of
/var/opengrok/etc/readonly_configuration-per_project_history.xml
looked like this:The source root had two projects, each with single Git repository, named
foo
andbar
. I ran two tests, one with global history on and per project/repository off and vice versa. Checked thelist
/minisearch
JSPs in debugger for each test.Also ran indexer with and without -H to make sure the history is disabled by default as before the change and also that the history cache is created if history is on (to test the
AnalyzerGuru
changes).Also tested in project-less mode.