Wednesday Jan 05, 2011

OpenGrok 0.10

We're proud to announce that OpenGrok 0.10 has just been released. See the release notes below for details on how to get it and what's new in this release.

OPENGROK 0.10 RELEASE NOTES

OpenGrok is a fast and usable source code search and cross reference engine. It helps you search, cross-reference and navigate your source tree. It can understand various program file formats (C, C++, C#, Java, sh, Perl, Python, ...) and version control histories like (Mercurial, Git, SCCS, RCS, CVS, Subversion, Teamware, ClearCase, Perforce, Monotone and Bazaar). In other words it lets you grok (profoundly understand) the open source, hence the name OpenGrok. It is written in Java.

For more details go to http://www.opensolaris.org/os/project/opengrok/

To download the binaries, please go to: http://hub.opensolaris.org/bin/view/Project+opengrok/files#HBinarysourcereleases and look for 0.10 binary, source or a package file.

This is a major update. It is advised that you cleanup your old DATA_ROOT (ideally remove it, or move it aside) and run indexing from fresh. Also the web application should be replaced, since the new indexes are not compatible with the old web application. Note that this also applies to upgrades from the 0.10 release candidate, since the format of the xrefs changed between the release candidate and the release.

For install help refer to the install wiki page. The discussions page lists forums and mailing lists where you can ask for help or discuss bugs or new features. Bugs should be logged in Bugzilla in the Development/OpenGrok category.

New features

  • python analyzer, perl analyzer
  • listing of variables/methods for quicker navigation
  • sh analyzer xrefs improved
  • SQL analyzer updated to SQL:2008
  • UI usability improvements
  • updated Lucene to 3.0.2
  • introduced Maven as alternative build system to Ant

Bug fixes

  • Bug #5590: Unhighlighted difference in compare list
  • Bug #11264: Add a python specific language analyzer.
  • Bug #13184: provide quick links to annotate,history and download from search results view: diff link for history search
  • Bug #13184: provide quick links to annotate,history and download from search results view
  • Bug #13777: Indexer should print "Adding: ..." before it adds a file
  • Bug #14545: clicking on annotate doesn't preserve line number
  • Bug #14663: broken syntax highlight in ksh script when ` is used (and when " is escaped)
  • Bug #14924: Java method calls incorrectly classified as definitions
  • Bug #15468: Log useful info from indexer regardless of -v
  • Bug #15661: OpenGrok should support new ksh command substitution x=${ cmd ; }
  • Bug #15890: Missing anchor in xref
  • Bug #15938: Analyzers should only use JFlex's public API
  • Bug #15947: Detect GNU CSSC in addition to SCCS
  • Bug #15948: Fail if svnadmin is missing: tests depend on it
  • Bug #15954: teamware repository not detected anymore
  • Bug #15956: indexer fails on indexing
  • Bug #15961: Allow certain symlinks to be followed to help with using clearcase dynamic views
  • Bug #16006: Indexer's -P option removes customization of existing projects
  • Bug #16070: our ctags parser fails to parse a c signature
  • Bug #16076: problem of ELFAnalyzer in opengrok 0.9
  • Bug #16334: Indexer hangs when files contain 0x1A characters
  • Bug #16370: build.xml: Check for JFlex.jar and taskdef for jflex-task use different classpath
  • Bug #16451: Tray app doesn't work with other protocols than jmxmp
  • Bug #16454: Trayapp shuts down when a window is closed
  • Bug #16465: SVN history of filenames containing @ cannot be retrieved
  • Bug #16481: NumberFormatException when opening Connection Settings the second time
  • Bug #16611: svn repository with svn:// protocol as urn results in NPE when reading history
  • Bug #16660: Perforce repositories return months 1-12, not 0-11
  • Bug #16677: revamp option -v
  • Bug #16692: Index files left open after multiple project search
  • Bug #16760: Generating incorrect links for C/C++ "#include" statements if extension of a header file is not on the lexer's list
  • Bug #16761: Perforce history reader would not use per-project clients (defined by P4CONFIG files)
  • Bug #16764: Perforce source annotation: the date is one month ahead, time information is not available
  • Bug #16772: status.jsp should be less chatty in production environments
  • Bug #16783: more.jsp garbles matches on lines crossing internal JFlex buffer boundary
  • Bug #16786: Control for User Information Provider URL (userPage)
  • Bug #16833: Subversion repositories disabled by default
  • Bug #16848: Search context is displayed in lower case
  • Bug #16883: ShXref should reset stack on reuse
  • Bug #16891: Unneeded files included in opengrok.jar
  • Bug #16892: Maven build includes management client source in jar
  • Bug #16893: Maven build includes SQLXref.lex
  • Bug #16909: Move JFlex generated sources to default location (Maven)
  • Bug #16913: OpenGrok fails to use JDBC cache if -R option is specified
  • Bug #16961: Definitions should have serialVersionUID
  • Bug #16986: Relative path for data root and source root has stopped working
  • Bug #17074: Home link no longer works
  • Bug #17127: OpenGrok leaving too many open files
  • Bug #17128: add more syntax highlighting styles and list all definitions/functions
  • Bug #17169: enable wildcard prefix search in OpenGrok script by default
  • Bug #17294: show progress on demand
  • Bug #17349: path needs to be percent encoded
  • Bug #17373: breadcrumb path needs to be URI encoded
  • Bug #17374: history links need percent encoding
  • Bug #17375: annotate link needs percent encoding
  • Bug #17376: download link needs percent encoding
  • Bug #17378: Please remove email obfuscation
  • Bug #17550: Malformed search for query with national chars
  • Bug #17551: Double-click on some project in project list doesn't work in Internet Explorer
  • Bug #17554: Empty "Navigate" window in Perl code
  • Bug #17582: context shown in hits doesn't show symbol type for non lowercased symbols
  • Bug #17631: Cookie name "OpenGrok/project" is a reserved token

For bug details refer to Bugzilla.

The road ahead

A tentative roadmap for OpenGrok can be found here: http://www.opensolaris.org/os/project/opengrok/Roadmap/

Contributors

We'd like to thank all the people who report bugs, send us ideas for improvements or contribute code. Below are just the people who sent patches or pushed code, but that doesn't mean that we don't appreciate your work. Reports and feedback from the users of OpenGrok is essential to make the developers able to continue improving the product. Note that this is just a summary of how many changes each person made, which doesn't necessarily reflect how significant each change was. Inspect the history log with hg log -v -r 0.9:0.10 to get all details.

68 Knut Anders Hatlen <knut.hatlen@oracle.com>, <Knut.Hatlen@Sun.COM>
39 Lubos Kosco <Lubos.Kosco@Sun.COM>, <Lubos.Kosco@Oracle.COM>
10 Jorgen Austvik <jaustvik@acm.org>
9 Trond Norbye <trond.norbye@gmail.com>
5 Patrick Higgins <patrick.allen.higgins@gmail.com>
3 Yuriy Vasylchenko <yuriy.av@gmail.com>
2 Leo Davis <ldavis@fonix.com>
1 cicicici <cicicici@gmail.com>
1 Martin Walsh <martin.walsh@oracle.com>
1 seadog <seadog1234567890@gmail.com>

Tuesday May 11, 2010

OpenGrok 0.9

OpenGrok 0.9 has just been released. You can find the source and binary distributions here: http://hub.opensolaris.org/bin/view/Project+opengrok/files

The MD5 checksums are as follows:

4faccd0b27ce65603f123f9d948f9498  opengrok-0.9.tar.gz
9ea28e6182f11ade75510c053518e685  opengrok-0.9-src.tar.gz
c11189d426a05f107bf9f3ab1b72994a  OSOLopengrok-0.9.pkg

OpenGrok 0.9 Release Notes

OpenGrok is a wicked fast source code browser. http://hub.opensolaris.org/bin/view/Project+opengrok/

OpenGrok is a fast and usable source code search and cross reference engine. It helps you search, cross-reference and navigate your source tree. It can understand various program file formats (c, c++, c#, java, sh, ...) and version control histories like (Mercurial, Git, SCCS, RCS, CVS, Subversion, Teamware, ClearCase, Perforce, Monotone and Bazaar.) In other words it lets you grok (profoundly understand) the open source, hence the name OpenGrok. It is written in Java.

Since OpenGrok 0.8.1 was released December 8, 2009 many features and fixes have been incorporated into OpenGrok in almost 100 commits for the 0.9 release.

New Features

  • Faster Lucene engine (3.0.1) underneath - faster analyzers
  • New jQuery (1.4.2) underneath - UI improvements
  • Support for xrefs with Unicode characters (not indexed yet, but finally viewable)
  • New SMF service - just pass the source root, the rest is taken care of by the service (Solaris/OpenSolaris only)

Bug Fixes

  • Bug #437 (partial): OpenGrok should support source files with multibyte characters
  • Bug #3435: C functions are not considered as functions
  • Bug #3900: Unexpected result when clicking a symbol definition
  • Bug #5042: Author field empty in opengrok after a multiple changeset push
  • Bug #5848: trimmed diff link results in NULL pointer dereference
  • Bug #6641: .txx file extension should be included in the list for C++ analyzer
  • Bug #9407: set limit for directory traversal during search for repositories
  • Bug #13185: broken focus
  • Bug #13280: RFE: Configurable tab size for xref
  • Bug #13330: Wrong URL when search for camel-case identifier has only one match
  • Bug #13362: plainanalyzer xref writer can never end for a file with long lines
  • Bug #13364: regression : Jar analyzer doesn't analyze the jars it used to for 0.7
  • Bug #13524: Color coding in diffs is confusing
  • Bug #13529: listing of a file (in xref) might take a LONG time
  • Bug #13777: Indexer should print "Adding: ..." before it adds a file
  • Bug #13884: IndexOutOfBoundsException in List2TokenStream.next()
  • Bug #13949: Missing line numbers in xref for XML file
  • Bug #13951: Wrong revision in info.properties when not building from head of trunk
  • Bug #13952: size output not correct
  • Bug #13961: no quick search box shown on windows (path separator problem in project names/IDs)
  • Bug #13996: build.xml should provide a version info for generated src.tar.gz so we don't depend on hg
  • Bug #13997: main logo should take you HOME ;)
  • Bug #14030: Many lines with same line number (regression)
  • Bug #14724: Incremental update of Bazaar history broken by instability in revision numbers
  • Bug #14757: pressing Enter on project select list box takes you to xref instead of submit of the search form
  • Bug #14953: history index for CVS repos should only include default branch if CVS/Tag is set
  • Bug #14978: upgrade lucene to 3.0.1
  • Bug #15004: Improved handling of UTF Byte Order Marks
  • Bug #15097: make the search bar in listing stay on top of the page
  • Bug #15114: AnalyzerGuru:stripBOM should not use String to avoid encoding issues
  • Bug #15240: radio buttons in history could behave like e.g. on wikipedia
  • Bug #15391: Executor should log the commands executed
  • Bug #15394: improve IPS package and SMF for OpenSolaris
  • Bug #15608: Search field should not be active in file display
  • Bug #15609: self organizing buttons in history view are confusing
  • Bug #15632: Strange results when searching for dotted identifier
  • Bug #15636: wildcard search for definitions does not work
  • Bug #15637: query constructed only for AND operators
  • Bug #15643: Simplify CLASSPATH in ogindexd
  • Bug #15644: Matching lines not shown when using single-character wildcard (?)
  • Bug #15652: history page shows a stack trace if file doesn't have a history
  • Bug #15690: css browser caching breaks UI
  • Bug #15858: String index out of range: -8161 from Summarizer
  • Bug #15859: html analyzer doesn't escape forms

For bug details refer to this list.

Known Issues

The back button does not always work as expected in Firefox. This issue is tracked in Mozilla's bug tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=565008

Contributors

We'd like to thank all the people who report bugs, and send us ideas and improvements. Below are just people who sent patches or pushed code. That doesn't mean that we don't appreciate your work. On the contrary, you are the people showing other people (who have the time to write code) what would be good to fix when you use this software and file bugs against it! Note that this is just a summary of how many changes each person made, which doesn't necessarily reflect how significant each change was. (Inspect the history log with hg log -v -r 0.8.1:0.9 to get all details.)

 45 Knut Anders Hatlen <Knut.Hatlen@sun.com>
 42 Lubos Kosco <Lubos.Kosco@sun.com>
  1 Chris Eldredge <chris.eldredge@gmail.com>
  1 Vitezslav Batrla <Vitezslav.Batrla@Sun.COM>

Friday Nov 20, 2009

OpenGrok 0.8 is out

After a long wait, OpenGrok 0.8 has finally been released! To find out what's new, take a look at the release notes posted on Trond's blog. Or just go straight to the OpenGrok website to download it.

From the release notes:

OpenGrok is a wicked fast source code browser. http://www.opensolaris.org/os/project/opengrok/

OpenGrok is a fast and usable source code search and cross reference engine. It helps you search, cross-reference and navigate your source tree. It can understand various program file formats (c, c++, c#, java, sh, ...) and version control histories like (Mercurial, Git, SCCS, RCS, CVS, Subversion, Teamware, ClearCase, Perforce, Monotone and Bazaar.) In other words it lets you grok (profoundly understand) the open source, hence the name OpenGrok. It is written in Java.

Since OpenGrok 0.7 was released October 17, 2008 a lot of features and fixes has been incorporated into OpenGrok in almost 300 commits for the 0.8 release.

Friday Nov 13, 2009

OpenGrok 0.8 RC1

Lubos has just built and posted the first release candidate for OpenGrok 0.8. See his announcement here. Please test it and give feedback on opengrok-discuss, or file bugs or enhancement requests on http://defect.opensolaris.org/.

It's a long time since the previous release (more than a year!), so we're of course eager to get all the bug fixes and the fine new features we've been working on out very soon now.

Apart from a couple of bug fixes, my main task for this release has been to implement the Java DB history back-end (bug #3624). This is a new cache layer on top of the code that talks to all the version control systems, and it can be used instead of the old XML-based cache. The XML-based cache is still the default, but Lubos wrote a nice section on how to set up the new cache in README.txt. If you try the Java DB back-end, you may notice that the initial indexing and generation of the history cache is somewhat slower, but that's compensated by the ability to update the cache incrementally later. Here's the full list of new functionality provided by the new back-end:

  • Incremental update of the history cache (bug #3052), so no need to retrieve and process the full history more than once
  • History for directories is cached
  • The history view shows which files were touched by the different check-ins

Other new features:

  • Ability to search across multiple projects has been reintroduced
  • Lucene back-end upgraded to 2.4.1
  • New scripts to simplify indexing and deployment
  • Auto-generated OpenSearch description enables web browsers to detect OpenGrok as a search engine
  • Several UI improvements

Friday Oct 17, 2008

OpenGrok 0.7 has been released

OpenGrok 0.7 was released earlier today, approximately six months after the previous release, OpenGrok 0.6.1. This release contains many new features, including:

  • Support for more version control systems (ClearCase, Git, Razor) giving a total of 11 supported systems
  • JMX agent that lets you monitor and configure OpenGrok more easily
  • Logging is now done with java.util.logging
  • Easier configuration of Subversion repositories
  • Smaller disk footprint for the history cache

OpenGrok 0.7 also incorporates many bug fixes, and a lot of effort has been put into cleaning up the source code, helped by tools like FindBugs, PMD, Checkstyle and EMMA. See the announcement for the full list of changes in the release.

One thing to note is that if you want to use the Git support, you'll need Java SE 6 or later because the Java wrapper around the Git binaries uses some constructs that are not compatible with J2SE 5.0. For the same reason, the released sources will not build unless you're using Java SE 6. This has been solved in the development sources, so if this is a problem for you, you should check out the source tree from the repository and build OpenGrok yourself. Everything else in OpenGrok should work with J2SE 5.0.

Tuesday Dec 18, 2007

SQL syntax highlighting in OpenGrok

Perhaps not the most frequently requested feature, but since much of the OpenGrok development happens at Sun's Database Technology Group these days (unofficially, that is, so please don't tell our boss that's what's keeping us so busy!), it's kind of embarrassing that OpenGrok doesn't understand SQL scripts. Now that's finally about to change. Yesterday, I checked in some basic support for SQL syntax highlighting, and we'll hopefully also be able to support search for symbols and definitions in SQL scripts in the next release. So then there should be one less embarrassment to worry about...
About

kah

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today