[BZ 1076104] Agent plugins don't require explicit purge to disappear
from DB.
[BZ 1076104] Server plugins don't require explicit purge do disappear.
Fixing API breakage
Cleanup of itests to not influence each other when setting server identity
and manipulating plugins.

Also fixed the PluginManagerBeanTest#isPluginReadyForPurge() by realizing
that other tests (that now correctly clean up after themselves) may have
already deleted the plugins that were marked to be deleted in the test
method the isPluginReadyForPurge depends on.
Removed unused method from local SLSB and some small docs updates.
[BZ 1072543] Unable to collect metrics from EAP 6 datasources when a system
properties is used in configuration

max-pool-size and min-pool-size metrics are now recoginzed by common code to
resolve a possible expression. BaseComponent.getValues has been changed in a
way, that we have more granular method called BaseComponent.getMetricValue
which handles single metric request. This method returns new enum called
ReadMetricResult which just represents a return code (if not Success, we may
want to know logical reason why metric was not collected)
[BZ 1080909] DynaGroup expression evaluator is not strict when grouping by
resource configuration property

Dynagroup expressions using  pluginConfiguration[prop] or
resourceConfiguratoin[prop] will now be matched 'strict' to property name.
Strict match in means resulting SQL would be 'simple.name = :argX' instead
of original 'simple.name LIKE :argX'.
BZ 1030082 1029384 - shutdown the server if it was decommissioned (that is, its server entry was removed from the server table)
[BZ 1088264] AvailabilityExecutor stops calling getAvailability() on
ResourceComponent after it previously failed with exception

The issue was in handling exception comming from future. When availability
check failed with exception we cought it, next run, just by calling
future.get() raises the very same exception. We forgot to mark future to be
rescheduled next time = setting it to null. This commit also makes exception
message more verbose so we know more what happened in plugin
Hiding the Resource Ancestry column in {Alerts|Events} Portlets not to overwhelm user with bazillion columns. It can be shown if necessary. Also fixing a typo that caused to displayed Group Events Portlet instead of Alert Group Portlet.
BZ 1080508 - make sure we set log level so the install doesn't abort
[BZ 1080470] - The unit in the new d3 charts is not refreshed correctly.
[BZ 1080470] The unit in the new d3 charts is not refreshed correctly. Adjust the YAxis over to accommodate large values due to scale changes
[1085270] Unable to install the RHQ server when calling rhqctl outside of bin directory
A fix for OS/X support.
Also, move debug_msg up to match the way it is in rhqctl.
BZ 1045496 - have installer be able to recover from a canceled install if its aborted while the EAR is being deployed.
[798006] Drift detection hangs on reading named pipes on filesystem
Protect against drift detection on not "normal" files.
Merge branch 'master' of github.com:rhq-project/rhq
[BZ 1089789] - Login Broken for GWT Dev Mode - Fixing the new login page for GWT development mode.
[BZ 1076126] - RFE: Canned dynaGroup expressions provided by plugin

Added concept of 'additional descriptor' (optional zml file living in
plugin's META-INF folder side-by-side to plugin descriptor). This file is
parsed only by server when plugin is discovered. Within this xml file, we
currently store predefined expressions for read dynaGroup definitions. Such
expressions can install dynaGroup definitions automatically. This commit
contains also logic which takes care about dynaGroupDefs created using such
expressions. When plugin updates such expression, dynaGroup is updated (same
for delete). GroupDefinition table has now "weak" reference to expression
(Plugin:ExprId)

Predefined dynaGroup expressions hardcoded in SingleGroupDefinitionView.java
have been replaced by cannedExpressions provided by plugins. From user
perspective, almost nothing changed, except cannedExpressions contain more
than just expression string, so when user selects template/expression fields
like name,description,recursive,recalcInterval are pre-populated as well.

Added 3 expressions. First groups managed servers by server-group name
(deploys DG) 2nd groups managed servers by hostname (aka domain) (deploys
DG) 3rd groups enabled deployments per server-groups

For expressions with 'createByDefault=true': dynagroups being created are
attached to plugin (having non-null cannedExpression). Whenever this
dynagroup is changed (via API or UI) it get's detached from plugin (setting
cannedExpression to null). Also on plugin upgrade or first install, if we
find a detached dynagroup having same name as we are about to create, we
just log INFO message - this happens when DG got previously detached.
[BZ 1076126] Update Group Definitions UI to show DGs from plugins

When listing dynaGroups we now show additional first column having an icon
of user - in case of regular dyna group or plugin - in case definition comes
from plugin. When user edits plugin-based definition we also warn him once
he attemts to save such expression. Within this commit i18n messages for old
template names has been removed.