MULE-7728: Fixed several clean up problems related to partitioned object storages.
SE-988 Thread Safety issues in one of the constructors of default mule session.
Merge pull request #836 from vromero/dev/vromero/bug/MULE-7742-2

SE-988 Thread Safety issues in one of the constructors of default mule s...
MULE-7620 - fixing broken tests cases because of lifecycle issues and mule client not using OutboundEndpointExecutorFactory
Merge pull request #837 from mulesoft/MULE-7620

MULE-7620 - fixing broken tests cases because of lifecycle issues and mu...
MULE-7620 - make AtomEntryBuilderTransformer not depend on the event parameter and use the message instead
Merge pull request #838 from mulesoft/MULE-7620

MULE-7620 - make AtomEntryBuilderTransformer not depend on the event par...
MULE-7728: Style fixes.
Merge pull request #835 from mulesoft/MULE-7728

MULE-7728: Fixed several clean up problems related to partitioned object...
MULE-7735:  Consumer caching should not be implemented in <jms:caching-connection-factory>
Merge pull request #841 from mulesoft/MULE-7735

MULE-7735:  Consumer caching should not be implemented in <jms:caching-c...
MULE-7697: com.arjuna.ats.arjuna.exceptions.ObjectStoreException when executen esireferenceimplementation on windows
Merge pull request #842 from mulesoft/MULE-7697

MULE-7697: com.arjuna.ats.arjuna.exceptions.ObjectStoreException when ex...
MULE-7751: Updated maven-deploy-plugin to version 2.8.1
Merge pull request #843 from mulesoft/MULE-7751

MULE-7751: Updated maven-deploy-plugin to version 2.8.1
MULE-7747 Add root project files to better Gnits standards compiance
Merge pull request #839 from vromero/dev/vromero/bug/MULE-7747

MULE-7747 Add root project files to better Gnits standards compiance
Modifications to improve fix for MULE-7620

- Conserve existing (asynchronous) behaviour for one-way
OutboundEndpoint’s created with EndpointFactory.
- Conserve the check to see if the Connector is started before
AsyncInterceptingMessageProcessor is invoked to avoid NPE and give
decent error.
- Remove the additional layer of complexity introduced with the
addition of DefaultOutboundEndpointExecutorFactory,
DeferredLaxInterceptionMessageProcessor, OutboundEndpointWrapper and
LifecycleAwareOutboundEndpointMessageProcessor.

Rather than introduce non-compatible changes and increase complexity,
the decoupling of OutboundEndpoint from it’s threading behaviour is
best tackled in 4.0 where we have more liberty to change and improve
API.  When we think about this more I am certain we’ll conclude that
DefaultOutboundEndpointExecutorFactory shouldn’t exist as a standalone
endpoint-specific concept in the MuleContext but rather it should be
the responsibility of the Flow to decide if one-way endpoints (and
connector operations!) should or shouldn’t use another thread.
MULE-7728: Fixed flaky test.
MULE-7728: Extracted constants in test case.