The console preview in the expression management and editing dialogues now show the currently configured style and filter match line length limits as coloured vertical lines. A warning is shown when one or more lines in the preview console exceeds one of these limits.
Matched lines can now be written to Eclipse's error log using one of the standard error levels.
Expression occurrences can be counted and displayed in a separate view.
Various user interface details were changed to be consistent with the official Eclipse guidelines. The expression dialogue was restructured into tabs.
Link behaviours are now referred to as "actions". "Link" is still used to refer to the clickable portions of texts to which actions can be assigned.
Expressions can now trigger popup notifications which display messages based on the matched console lines even when Eclipse is not currently the active window. An action which is triggered when the user clicks the popup can be configured.
Expressions can now play sounds when they are matched.
Expression items may now have a quick expression which is tested before the main expression is evaluated.
A base path for relative file links can now be specified. By default, the project's root directory is used.
URLs without a schema prefix can now be used in URL links. They will automatically be prefixed with "http://".
For file and Java links, an optional character offset can be specified to position the cursor at a specific column in the editor.
Pattern strings in link configurations can reference use Eclipse variables (as used in the arguments tab of the launch configuration dialogue).
Groups of expression items can now be assigned custom names. These names can be used in link pattern strings.
By default, the Grep View now uses the same colours as the Eclipse console. These colours can be changed in the preferences.
On Mac systems, the link modifier key is now Command instead of Ctrl. The modifier key can be changed in the preferences.
Items can specify autostart links, which will open automatically whenever a line matching the item's regular expression is written to the console. Autostart links require the Grep View to work.
Lines filtered to the Grep View can be completely rewritten. Rewritten lines can include any parts of the original line and may have different styles and links than the original console output.
Expressions may now match multiple substrings per line. Previously, only the last match in a line was recognised.
Expressions and capture groups may now be assigned links. These links will be executed when the matched substring is clicked on while the CTRL key is pressed. Different link types can be used to open text files or Java types in the Eclipse editor, open URLs in a browser or execute scripts and system commands.
The expression dialog now contains a web link to the Java Pattern API documentation (explaining the regular expression syntax).
An optional second regular expression can be configure for each item to prevent the item from being considered a match for certain strings even if the main expression matches.
Case sensitivity of grep expressions can now easily be toggled via a checkbox.
The Grep View context menu now provides an action for jumping to the selected line in the original console.
The Grep Console tab is now available for JUnit, Eclipse RCP and CDT launch configurations.
The Grep Console bundles and packages have new IDs. That means that if you had an old version of Grep Console installed, it was not replaced when you installed 3.0. In this case, it is recommended that you uninstall your old version manually. Your old settings are automatically imported by Grep Console 3.0.
Grep expressions can now be arranged in folders for better overview. Each folder can be enabled or disabled as a whole.
Highlighting settings are now configured separately from the grep expressions that use them. These styles can be shared among multiple grep expressions.
Grep expressions and styles can now be exported to XML files for sharing or transfer to other Eclipse workspaces.
Grep folders and expressions are configured globally, but they can be individually enabled or disabled for each launch configuration.
The Grep View displays a console like text field that shows only a
subset of
The length of string lines that are tested with the regular expression matchers may be configured in the preferences. This became necessary as very long lines could have a significant performance impact when tested for the Grep View.