1.7.18

• fix opengrok-mirror configuration check for configs with overridden commands

1.7.17

• fix commands check in opengrok-mirror
• fix regression in selecting projects with space in the UI
• add timeout for generating single xref
  • added xrefTimeout indexer tunable

1.7.16

• fix UI problem with displaying revisions in annotation view

1.7.15

• fixed Git submodule detection
• insufficient permissions are now properly reported in the web app

1.7.14

• added historyCachePerPartesEnabled indexer tunable to disable history cache generation in chunks
  • use this if you have giant repository (say hundreds thousands of changesets) and care about indexer performance and can assign lots of heap memory to the JVM running the indexer (say tens of gigabytes)
• commands section of the opengrok-mirror configuration is now properly checked
  • also in Docker: failure leads to sync being disabled
• fix e-mail address detection in Go sources
• Subversion no longer required for building OpenGrok

1.7.13

• API used in Python tools now properly reports HTTP errors
• handle API error in Docker properly

1.7.12

• bump history chunk size
  • currently this is 128k changesets for Mercurial and 64k changesets for Git
    • the new historyChunkSize indexer tunable can be used to override this globally. Generally this should be needed only when working with very large repositories (think millions of changesets or high number of changesets that touch a lot of files) or when trying to drive the heap usage down radically (at the cost of increased indexing times) or when indexing many sizable repositories in parallel (the higher parallelism level the higher heap requirements). For the tunable, the semantics is: the higher the number, the higher memory consumption (depending on the size of the repository, i.e. number of changesets and the number of files touched by each changeset) and speed will be (assuming there is enough heap space available).
• Lucene 8.9.0
• per user settings
  • currently allows to disable the suggester

1.7.11

• better parallelization of the creation of history cache
  • the indexer option --historyRenamedThreads was renamed to --historyFileThreads
  • if using the -G indexer option to generate the tags, it is necessary to regenerate history cache from scratch (remove the historycache directory under the data root and re-run the indexer)

1.7.10

• webapp fixes

1.7.9

• smaller resource conservation fixes for the web app