This is the release candidate (=CR) of the upcoming RHQ 4.0 release. It is meant for interested parties to have a look at the new GUI, to see the GWT technology in action, and to test so that we can get feedback before the final release.
If you previously used an earlier RHQ 4.0 developer preview release, you must clear your browser's cache prior to using the RHQ 4.0 CR GUI! For example, in Firefox, press Ctrl-Shift-Del and then choose to clear everything from the cache.
While this is a CR release, it is labeled as -SNAPSHOT and will unzip into a folder named -SNAPSHOT.
You can not auto-upgrade an agent from the previous beta1 release to this CR.
It may be possible to upgrade from this CR to the final release, but you must not count on it.
new SmartGWT-based GUI
100% AJAX Web 2.0
internationalized (CR only includes English localized messages)
multiple customized dashboards can be saved
enhanced scheduling for operations, including support for cron expressions
"message center" provides a history of GUI messages from the current session
configuration editor now supports editing lists of simple properties
support for Postgres 9.0
support for deleting agent plugins
support for executing an RHQ CLI script when an alert fires (for more info, see this blog)
improved authorization for content repositories - public/private repos, repo owners, and MANAGE_REPOSITORIES privileges
User documentation on the RHQ wiki has not been updated yet - it still documents RHQ 3.0.
Some error messages will be masked and instead print "InvocationTargetException: please see server log for more details", but the server log may not necessarily provide more details.
The installer shows some non-replaced {} properties.
Some properties are editable when viewing a configuration in read-only mode.
Clicking the Reset button in the user or role edit view results in an error.
For a list of issues that still exist in the very latest RHQ 4.0 code, see Bugzilla.
Please report all bugs you find in Bugzilla. If you find a bug that has already been recorded in the above list, please leave a comment on the bug, especially if this needs special steps to reproduce.
You can download the release here.