updated patternfly.css version + fixed menubar look in firefox (now both safari and ff should look same)
[Bug 1101166] Buttons are not aligned properly and not visible in alert
definition creation page

Disable another interfering pieces in patternfly.css
fixed main menu link colors when not yet :visited
Throw ResultFailedException only in case we really only failed to read
requested attribute but we succeeded to connect and authenticate

this fixes issue introduced by PR23: agent log was incorrectly spammed by
warn avail messages when standalone or domain EAP6 was turned off.
Bug 1099220 - jbossas7/jmx/ApplicationMBeansDiscoveryComponent does not work with WildFly8

Updated port discovery (use HTTP management port with Wildfly standalone
and HTTP application port with Wildfly managed servers in domain mode)
Upadted remote JMX url builder (use "http-remoting-jmx" transport with
Wildfly servers)
Updated sample plugin POM file

Tested on EAP6 standalone and domain
Tested on Widfly 8.1.0.CR2 standalone and domain
[BZ 1069691] (JON3-25, PRODMGT-368) DomainDeployments should be managed in a
single menu option in domain mode

Deploymet resource has been removed from Server-Group level. Now we have
only DomainDeployment (living under DC) and Deployment (discovered under
ManagedServer). We manage everything related to ServerGroups within
DomainDeployment's configuration and operations. Operation 'promote' remains
(although not needed anymore)

To assign DomainDeployment with Server-Group user adds new Configuration map
item, select SG, runtime-name and enabled/disabled state.

To enable/disable deployment on given SG user edits particular configite and
changes enabled boolean attribute

To remove DomainDeployment from SG user just removes given map item.

Given domain deployment cannot be assigned to same server group more than
once (even with different runtime-name) - EAP restriction. runtime-name
cannot be changed on existing map items (it's documented and ignored)

New operation for DomainDeployment resource called 'restart' was introduced.
User can restart deployment in particular SG or in all assigned SGs.

DomainDeplooyment's getAvailability() was also changed to return MISSING
instead of DOWN when deployment is not found on EAP.

DomainDeployments get discovered only under master DomainController, not
slave HostControllers
[1079225] Graphs of sub-level resources in groups fail
API's dealing with Resource Groups should typically handle all 3 types of
resource groups: standard, autogroup and autoclusters.  The way to do this
is to use an EntityContext in the API.  In this case we were ignoring
autoclusters.  This fix converts a few group-related APIs to use
EntityContext. It simplifies the APIs, fixes this bug and likely fixes
a few other problems.
[552112] Add time column to Suspect Metrics page
A 4 year old request but still useful, and we aim to please.
fix test failures
new MenuBarView styling
Itest for logging in without a role.
[BZ 1101770,1101773] make sure we do not process agent commands
fix test failure
some minor code cleanup
on HosctController component hold info if given HC is DC as well

This value is updated on component start and also by availability code, when
going from DOWN to UP (to handle cases, when HC was reconfigured to DC)
Access to HC Component property is synchronized, because value is updated by
avail code and can read by discovery code
[BZ 1069545] - addendum to subcategory work
When removing tables from our schema those obsolete tables must be added to
obsolete-schema.xml in order to properly support db overwrite.
- This should also fix test failures resulting from this omission in the
  original work.
Merge pull request #40 from lzoubek/feature/JON3-25

[BZ 1069691] (JON3-25, PRODMGT-368) DomainDeployments should be managed in a single menu option in domain mode
[BZ 1015706,1092756] check for invalid max and update it with the avg

We also log a warning to indicate that we have come across an invalid metric.
We then update and persist the max.

Conflicts:
	modules/enterprise/server/server-metrics/src/main/java/org/rhq/server/metrics/MetricsServer.java
Remove protection from weird metrics like avg > high or avg < low now that BZ1015706, and BZ1092756 are fixed.
Looks like I had already removed the high value check but still had the low value check in place.
[1103375] Viewing operation details for operations with no results throws uncaught exception in GUI
- Handled cases where null results are returned from an operation excecution.
- Fixed one op history update path where [results] data could be lost.