[BZ 747925] now that we fixed the metadata update stuff, we are putting the jmx plugin's descriptor metadata back the way we want.
See https://bugzilla.redhat.com/show_bug.cgi?id=747925#c13
Completely remove unused FileContentDelegate functionality. Align functionality with similar file content classes.
organize the .classpath entries - put the source modules up top.
add shrinkwrap/arquillian libraries as well as liquibase
[BZ 682255] Inconsistent titlebars. Add IconEnum for typesafe icons.
Merge branch 'inventoryTab'
switch very noisy log message from DEBUG to TRACE
minor: fix mistake in javadoc
[BZ 799532] do not attempt to attach to java processes running as different users than the Agent, since it sends SIGQUIT signals to the java processes causing them to spew thread dumps to their stdouts, and it fails to attach to them to boot (https://bugzilla.redhat.com/show_bug.cgi?id=799532); turn down logging in JMX discovery component - log most things at DEBUG, not INFO
Bugfix for previous commit: 413c72e
Merge branch 'inventoryTabViewNameConsolidation'
typo
[BZ 800570] set Content-Type header to "text/plain", rather than not setting it at all, in sessionAccess servlet responses - this prevents errors in FF's error console when FF tries to parse the response as HTML (https://bugzilla.redhat.com/show_bug.cgi?id=800570)
There was a problem with backfilling. Disabled resources should
remain disabled despite an agent going down, or being suspected
as down.

Fixing this issue brought to light inherent weaknesses in
the legacy "No Availability Records equals Unknown" special
case.  So, bit the bullet and we now ensure an initial
Availability and ResourceAvailability record exist at Resource
persist time. The initial Availability is UNKNOWN, with a start
time of 0 (epoch), indicating that we have no avail history for
the Resource.  The initial Availability will typically be
replaced fairly quickly, when an agent reports th first actual
avail for he resource.

But, the existance of the record makes several things easier to
handle and to understand, and hopefully makes sense to the
user as well.

Also, fixed both a legacy logic error and a legacy coding error
in mergeAvailabilityReport, when performing an "insert" of past
avail data.

Updated tests to handle the change in strategy.
Add initial support for remoting and jgroups
Managed servers are now removed with the normal remove resource method.
Related to Bug 800580
- Add obsolete=true to RHQ_DRIFT_TEMPLATE_MAP. Instead of getting
deleted it's potentialy getting created.
@BeforeDiscovery can now be targetted to only certain test methods.
Multiple @BeforeDiscovery methods can be explicitly ordered.
Changes to @RunDiscovery handling:

- Automatically determine the number of times discovery should run in agent
mode based on the resource type hierarchy depth.

- Changed the defaults to run both the server and service discovery.
[Bug 800580 - 4.3 db upgrade failing if existing db does not have RHQ_DRIFT_TEMPLATE_MAP table]
The dropTable SST command did not honor ignoreError="true" and
would kill the upgrade step if the table did not exist. This
fixes that issue.
Fix test issues due to the introduction of a built-in Availability
record present on all new resources.  Since a resource's
Availability records may be numerous they are not cascade deleted,
meaning tests need to ensure they are cleaned up manaually.