[3.5. M4] Separate MULE_HOME and MULE_BASE

Summary

Some users and the Mule Studio team have requested the ability to split the contents of the MULE_HOME directory in two:

• A read-only static part containing the artefacts that can be safely shared across apps. This would be called MULE_HOME
• A dynamic part containing the artefacts that are exclusive to each app. This would be called MULE_BASE

#Contents

MULE_HOME

Directories:

• bin
• data-mapper
• docs
• examples
• lib
• plugins
• src

MULE_BASE

Directories:

• conf
• domains
• logs

Configuration

The path for each of these folders will be specified through system properties MULE_HOME and MULE_BASE. Notice that currently Mule startup scripts take the MULE_HOME property and propagate it to the JVM as mule.home. The same pattern will apply to the MULE_BASE which will be propagated as mule.base.

If mule.base is not specified then it will be defaulted to mule.home