[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'.
[1060353] Non required or unused properties in rhq-server.properties are being required by rhqctl
Make the unused oracle props optional and remove them from the supplied
rhq-server.properties file.
[BZ 1069667] - (JON3-17) Make JON login look like other Red Hat products - First prototype. Using the PatternFly default logo.
[BZ 1069667] - (JON3-17) Make JON login look like other Red Hat products - RHQ branding & handling error cases during login process.
[1061311] rhqctl contains user modifiable values that result in an unsupported rhqctl script
Introduce rhq-server-env.bat.  Analogous .sh file coming in subsequent commit.
[1060353] Non required or unused properties in rhq-server.properties are being required by rhqctl
Remove some related special-case installer code.
[1061311] rhqctl contains user modifiable values that result in an unsupported rhqctl script
Introduce rhq-server-env.sh.  Now environment variables are set outside of the
actual scripts used for installation, etc.
[BZ 1073096] - Adding "-h" as a valid help option to isHelp() method.
BZ 1080472 - The unit in the new d3 charts is not refreshed correctly.
Fix the bug that improperly calculates the units of measure on the Y-Axis and on Min Value of chart legend.
Bug 579810 - Collection of Postgres table metrics fails when the tables are not in the public schema

Changed resource key format ("tablename"->"schemaname.tablename")

Implemented resource upgrade and updated resource component and discovery component

Also changed the availability check: new the resource component checks for table existence instead of looking at the parent database availability
Bug 1079403 - Postgres Plugin - Table Vacuum Fails

Changed sql query to include the schema which the table is part of.

Also updated table component #invokeOperation method to use connection pooling support
Bug 1082747 - Postgres Plugin - An Invalid Server Configuration Status Should Not Be Stack Trace

Throwing an Exception is the only way a plugin component can fail the process of starting of a resource. So without changing the agent plugin facet we can't rely avoid the stack trace shown on the server.

Still, the stack trace shown when a Postgres server resource is configured with invalid credentials was particularly long, so I changed the plugin component implentation to make the server show a stack trace with no cause and a condensed message ("Invalid password").
[1061311] rhqctl contains user modifiable values that result in an unsupported rhqctl script
Add logic to 'rhqctl upgrade' command to copy rhq-server-env.sh|bat from the
old to new server, if it exists.  The old, potentially edited, version will
be used and the new version will be backed up for reference in case it has
new env variables and/or documentation.  This behavior is analogous to what
we currently do for rhq-agent-env.sh|bat during an agent update.

Also: fix an upgrade problem with server stop at the end of the upgrade.
[BZ 1069667] - Adding CAPS LOCK detection and version is now taken during the build time using mvn filtering.