[BZ 1005922] - Selecting grouped fired alerts in chosen time range does not work - hiding the filters if the alerts are shown in the grouped mode and vice versa.

(cherry picked from commit 3c5dc0d98419a209df10a832259e85cfc1608c98)
Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
[1060223] Bundle deployment in JBoss ON 3.2.0 when using Oracle as a backend fails with ARJUNA016061 exceptions
This is a completely different problem from the "no-tx-separate-pool" issue
already fixed for this BZ.  The addition of that DS attribute led
to this issue involving the XA DS and our [quartz] job scheduling
and triggering.  The issue had to do with interactions between our
scheduling of resource bundle deployments, our scheduling of the
umbrella bundle deployment status checking job (which came into
existence as a fix for Bug 1003679), and possible fast reporting
of a bundle resource deployment status from an agent.

The solution is to ensure that the bundle deployment status checking
job is scheduled after the bundle deployment scheduling has been
fully committed and the individual bundle resource deployments have
been scheduled.

Furthermore:
 -  don't use a repeating quartz trigger, as this seems to exacerbate any problem that may occur.
 -  when scheduling an operation minimize any access time on the quartz tables.

Cherry-Pick of Master 4fec3d53f49f4fc6e941983484ae80c4a9e1a271
Signed-off-by: John Mazzitelli <mazz@redhat.com>  (review)
Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com> (cherry-pick)
[BZ 1037809, 1024526] Fix for agent file permissions and related umask settings.

Signed-off-by: Libor Zoubek <lzoubek@redhat.com>
[BZ 1037809] Add code set the default umask if the user makes a mistakes and removes the definition from the env script.

Signed-off-by: Libor Zoubek <lzoubek@redhat.com>
BZ 1014622 the suspect metrics report screen doesn't filter out ignored resoruces.

this commit only shows those resources that have been COMMITTED - anything else won't show in the suspect metrics view

Cherry-Pick of master c954eda
Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com>
[BZ 1037809] Rewrite default umask code to a more traditional shell script syntax to avoid incompatibilities with older systems.

(cherry picked from commit a18b558af3479687d89392bdb7bc99bac4d00f8b)
Signed-off-by: Libor Zoubek <lzoubek@redhat.com>
[BZ 1040712] - Attempting to delete a previous bundle deployment from a destination fails due to database foreign key constraint violation - Redirecting the reference of replaced bundle to the doomed one (just like removing a element from a linked list). Adding an itest for this use case.
(cherry picked from commit 08b1215bd377333c118b7dce88c09b30f37de409)

Signed-off-by: John Mazzitelli <mazz@redhat.com>
[BZ 1040712] - Attempting to delete a previous bundle deployment from a destination fails due to database foreign key constraint violation - Removing an unused finder constant.
(cherry picked from commit c52692223c019967238adb531c23114cf2991850)

Signed-off-by: John Mazzitelli <mazz@redhat.com>
[BZ 1026473] When upgrading bundle with compliance=full deployment folder
still contains empty directories not found in bundle

This patch adds support for handling directories in bundle-deployment client
side. The impact is only for doing updrade or revert (not initial deploy).
FileHashcodeMap.rescan now reports every single directory with special HASH.
Then in Deployer code we need to fill it directories to 2 other maps
(original=from hashcodes.dat, newFiles=from bundle content). Then when
processing diff we have to sort items to be backed up/deleted and process
them in reverse order. (Then if there is 'dir/file', then 'dir/file' is
processed before 'dir'). Finally backup for dir is just creating it in
backup directory. Several tests have been fixed - especially directories now
appear in diff additions together with new files. SimpleDeployerTest has
been updated to test empty dir handling.
(cherry picked from commit d306411243c361b1fb3a009e6d959447322c3b5f)

Signed-off-by: John Mazzitelli <mazz@redhat.com>
[BZ 816598] - "Failed to load resource composite data" message is incorrectly logged when already logged out user tries to browse resources - Enforcing the login dialog if the user is logged out (instead of throwing an exception). When logged out from a different browser tab, it takes about 3 seconds to propagate this information to the other tabs, however this is really an edge case. NOTE: If the login dialog is displayed on multiple browser tabs and user logs in to each of them separately, it will create multiplse independent sessions that doesn't affect each other. Now if user logs out from a tab, it doesn't do anything to another tabs. This bug is about "forking" the user session by opening a new tab from the original web UI.

(cherry picked from commit 4ec41696e0b3271bfd3d78fa1f5a57e08d4f88c2)
Signed-off-by: Libor Zoubek <lzoubek@redhat.com>

Conflicts:
	modules/enterprise/gui/coregui/src/main/java/org/rhq/coregui/client/util/rpc/TrackingRequestCallback.java
[915532] [apache] Unable to discover Apache httpd on Windows if Include...
Revision of fix in commit 3d9cdf6d9d7eae5643ff270816b236ba0dc74f9b after review.

(revised fix)
    Apply fix based on Larry O'Leary's suggestion in the BZ. Localize the
    change to a windows-only block in Glob.rootPortion such that all callers
    benefit and non-windows is unaffected.

Conflicts:
	modules/plugins/augeas/src/main/java/org/rhq/augeas/util/Glob.java

Cherry-Pick of Master 213f42ae56da1215cf57bc56bf05dfcbe28e11c7
Reviewed-by: Larry O'Leary <loleary@redhat.com>
Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com>
[BZ 1005951] ScriptServer resource availability regular expression matching
fails due to complete string matching being applied to multiline output

Fixed by changing to Pattern.matcher().find() instead of String.matches.
Users do not need to write long or crazy regexes to find match in multi-line
output. Previously you'd write `(?s).*OK.*` to match 'a\nb\nOK\n' now just
use `OK`

Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com>
[BZ 1005951] ScriptServer resource availability regular expression matching
fails due to complete string matching being applied to multiline output

Improved description for availabilityOutputRegex config property.

Cherry-Pick master 62cc988c8980a15e00b61fc45370f76c10a3608f
Signed-off-by: Jay Shaughnessy <jshaughn@redhat.com>
Upgrade exec maven plugin to a version hosted on the JBoss Nexus repositories.
 Update rhq-enterprise-jar for independent versioning.
 A few more updates for rhq-core-native-system and version documentation.
Inherit plugin repositories from root pom rather than override locally.
 Updare rhq-core-plugin-api for independent versioning.
 Update rhq-core-util for independent versioning.
 Modify rhq-remoting-client-api for independent versioning.