Uses a wrapper to catch the return value instead of the ExecuteException
Remove commented lines
Tabs hopefully removed now..
BZ 987628 - Agent can block indefinitely at startup

It appears the agent doesn't care that registration fails. The agent will
simply retry 5 times every 10 seconds, then the agent will block forever
waiting for the server to ping it, which won't happen.

This change basically forces a complete shutdown after registration fails and
displays an error as such.

There are a couple of cleanup things done for concurrency reasons as well.
BZ 987628 - Agent can block; Mars Rover behavior - retry forever

This patch makes the agent continue to try to connect, except in these cases:
1) The Agent object fails to construct.
2) The Agent is not the right version and cannot upgrade.
3) The Agent lost its token or has the wrong token
4) 'HelpException' - which happens through the command line interface
Throw exception if agentStatus returns value other than 0,1 or 3
BZ 987628 - if the agent isn't registered BUT it hasn't been able to even talk to a server yet, keep waiting.
Bug 1059882 - Cluster-connections, bridges and JMS connection factories must define either connectors or discovery-group but not both

From 6.1 on, EAP has a guard which refuses modifications on these resources which include a value for both attributes, even if one of them is null. AS7 plugin had some code in ConnectorDiscoveryGroupValidatorComponent to check that both values were not filled, but allowed sending nulls or empty String.

Now in ConnectorDiscoveryGroupValidatorComponent configuration update happen in two phases:
1. execute a composite operation to set one of the two attributes and unset the other one
2. use the standard ConfigurationWriteDelegate for all other attributes

Side work: update ResourcesStandaloneServerTest and ResourcesDomainServerTest to exclude some resource types which are broken in some versions of EAP.
BZ 786082 - tomcat as a service is not properly detected.
[BZ 1005922] - Selecting grouped fired alerts in chosen time range does not work - When switching grouping on, the values of the range filter are stored and the filter is reset in order to fetch all the data (when grouping is on, no filtering can be applied). Similarly, when switching it off, the values are loaded from previously saved filter and applied as start/end date for filtering of alerts.
Merge pull request #7 from rhq-project/bug/987628

Bug/987628 - allow agent to die  if it can't register
Bug 918207 - Add missing agent service definition in org.rhq.core.pc.PluginContainer#services
Also adjust the init.d for tomcats.
[1058534] Alert template for Trait Change from older RHQ results in NullPointerException
The "Changes" operator requires slightly different logic as alertConditionValue allows null
Add null handling, also refactor some similarly verbose/confusing code
in a few CacheElement classes. And add i-test for this issue.
BZ 690957  EWS Tomcat installed from RPM shutdown fails.
BZ 1069880 -  Discovery of Tomcat fails when started using daemon.sh or jsvc
Merge pull request #8 from jfclere/master

BZ 786082 - tomcat as a service is not properly detected.
Merge pull request #10 from jfclere/BZ690957

BZ 690957  EWS Tomcat installed from RPM shutdown fails.
Upgrade to Sigar 1.6.5.132-6 that includes the arm version of the native lib.
 Increment apache commons fileupload to 1.3.1.