Upgrade to jolokia 1.2.0
FABRIC-947: Fixed jboss-fuse-minimal to start and create a fabric in offline mode.
fixed link to irc chat logs
fixes #699 for latest link to IRC log
#877 properly search/replace csv files for package names
#877 remove old xls to fix the integration test
Cleanup gatway-fabric to use component coding conventions
Add update method to FabricJaasRealm.
Add onFailed callback to "wait for provisioning" operations, so that we can gather as much information as possible about the failure. Misc test improvements.

Conflicts:
	tooling/testing/pax-exam-karaf/src/main/java/org/fusesource/tooling/testing/pax/exam/karaf/FuseTestSupport.java

Conflicts:
	tooling/testing/pax-exam-karaf/src/main/java/org/fusesource/tooling/testing/pax/exam/karaf/FuseTestSupport.java
Configure pax logging in itests, so that child containers store their logs under the parents log folder (retain the logs after child is destroyed).
Ensure example-camel-cluster.server waits for the jetty component. ExampleCamelClusterTest now uses a more accurate way to check that failover works.
MQ itests now display the home folder of the container as part of the boot message.
Add more verbose logging when updating the git master url. Validate the git master url before notifying listeners.
Make the timeout for "wait for container alive" configurable.
Improve Provision testing utilities. Add uni tests for Provision and WaitForProvisionTask.
Fix issue with WaitForProvisionTask that could end prematurely. Improve handling of timeout.
Ensure that Container instances in itests always use a ServiceProxy of the FabricService.

Conflicts:
	fabric/fabric-itests/common/src/main/java/io/fabric8/itests/paxexam/support/FabricFeaturesTest.java
Align with master.
FABRIC-730 product integration tests for validating feature definitions

The tests run the container and iterate through all available, not
installed features. Each feature is being installed and all the problems
are reported to STDERR.

TODO: investigate the problem why consecutive uninstallation usually
causes problems (both with next installations and with the PAX test
system itself - "no such object in table" exceptions).
FABRIC-730 ignoring failing tests for now