Vladimir Kotal

Also it would be nice to get the path descriptions (`eftar`).

> Directory-aggregated #Lines and LOC is coming soon BTW sunglasses Oh cool. Just went through the code that deals with "extras".

The search API endpoint produces `SearchResult` which is basically a wrapper for list of `SearchHit` objects. These contain just a line and line number as documented on https://opengrok.docs.apiary.io/#reference/0/search/return-search-results

Interestingly `opengrok-indexer.pom` has the `annotations` artifact at 20.1.0 and the web app has also another version: ``` # find /var/tomcat8/webapps/source/ -name 'annotations*.jar' -type f /var/tomcat8/webapps/source/WEB-INF/lib/annotations-12.0.jar /var/tomcat8/webapps/source/WEB-INF/lib/annotations-20.1.0.jar ``` Looks like one...

I can see this only when Tomcat is restarted. For the record, the only other applications are the `manager` and `host-manager`.

Going through https://mvnrepository.com/artifact/org.jetbrains/annotations/19.0.0/usages?p=1 I noticed chronicle-map related artifacts. Namely chronicle-bytes-2.20.80.jar depends on annotations-19.0.0.jar. Even the latest version of chronicle-bytes-2.20.105 depends on annotations-19.0.0.jar so upgrade will not fix that.

When this started happening ? what exactly has changed ? Could you try the latest 0.13 RC ?

Also, do the directories with git repos have any subdirectories named `RCS` ?

The indexer will not send the config to the webapp if `OPENGROK_WEBAPP_CFGADDR` is set to `none` in the `OpenGrok` script. It might be sufficient just to copy the contents of...

Could you post the structure of the directory ? I wonder if there is a way how to make the RCS repository detection more reliable. Normally there are files with...