Replies: 4 comments
-
The data to generate the Navigate window is part of the xref and generated via The definitions originate from a ctags run on given file. Either the ctags run is done in the context of indexing and the definitions are stored in the index or they are determined dynamically if the xref is generated on the fly, e.g. here: So, if the same file has different definitions on multiple deployments, I'd look into differences in the defitions ctags generates. Is the ctags version same on these deployments ? Also, one thing to note: currently if you display the xref for historical versions of given file (by clicking on the revision number in the history view) the navigate window will be empty. I'd have to see why it works like that. As for reindexing a sub-project, this is not possible. The granularity for indexing is per project. And that requires special workflow (see https://github.com/oracle/opengrok/wiki/Per-project-management-and-workflow). |
Beta Was this translation helpful? Give feedback.
-
To have the Navigate window display tags (definitions, ...) for historical versions of the file in the Navigate window, it is necessary to enable ctags run in the web application, by adding these web app tunables to the configuration: <void property="ctags">
<string>/usr/local/bin/ctags</string>
</void>
<void property="webappCtags">
<boolean>true</boolean>
</void> e.g. via read-only configuration when running the indexer. |
Beta Was this translation helpful? Give feedback.
-
Now, it would be nice if the xref writer could handle the case of |
Beta Was this translation helpful? Give feedback.
-
Hi Vlad, thank you for your response. Yes, the ctags version is the same across the deployment as I use the same environment settings and the script to generate the indexes. I will try to reindex the project and see if it helps in going past this issue. |
Beta Was this translation helpful? Give feedback.
-
We are seeing an issue where the indexing for a code base would finish but some of the indexed Java classes would show an empty Navigate pane like this:
The same Java class in another version that is indexed in the same way would show the contents in the Navigate pane.
I am thinking that a reindex would probably fix the issue but I am not very certain it would. However, I wanted to give it a try.
So currently I index my projects using the following settings:
My source directory structure would look like
During the indexing command like above, I specify the -s argument to be /MainLine_A for example. Then I get a nice split of subprojects just like above when searching code on the Opengrok app.
If the problem is with let's say a code file in "subprojA6", can I selectively reindex this sub-project only without having to reindex the whole codebase?
Thanks!
Vinay Chilakamarri
Beta Was this translation helpful? Give feedback.
All reactions