OpenGrok
- a wicked fast source browser

Known Issues ...

  1. Due to Exuberant ctags bug 1324663, OpenGrok might keep waiting for ctags. Workaround is to ignore the problem causing SQL files with -i option to OpenGrok.
  2. Due to Exuberant ctags bug 1187505 ctags fails to recognize certain definitions. So OpenGrok will not be able search these
  3. If the indexing using opengrok.jar (or run.sh) is interrupted in the middle, a lucene lock file is left over; next time you run the opengrok.jar, it would give an error message saying "Lock obtain timed out ...". It is OK to remove the lock file mentioned in the error message and run the indexer again, if no other processing is trying to update the Lucene index (fixed in 0.7)
  4. Indexing is a memory intensive process. If you get "java.lang.OutOfMemoryError: Java heap space" error, try the -Xms<size> option to java (Eg java -Xms128m)

 Also be sure to check out bugs logged against Opengrok.

Unstable usage page

 Since {OpenGrok is still in development, please check the development trunk usage info(CommandLineOptions class) first (or run opengrok.jar with -?) for a list of all possible parameters one can pass to opengrok.jar file.

Internal defaults of a configuration can be found in Configuration class.

last modified by taz on 2009/11/22 06:06
Collectives
Project


© Sun Microsystems Inc. 2009
XWiki Enterprise 1.8.2.19075 - Documentation
Terms Of Use | Privacy | Trademarks | Copyright Policy | Site Guidelines | Site map | Help
Your use of this web site or any of its content or software indicates your agreement to be bound by these Terms of Use.