jExperience and Jahia definition checks

Note

Starting with Jahia 8.1.2.0, Jahia is checking if upgrading the module introduces changes in its definition. If such changes are detected, the default Jahia behavior will be to reject a module upgrade.

jExperience comes with its own migration mechanism to handle changes in definitions, when updating jExperience via Jahia's module manager, it is therefore safe to ignore definition checks via the UI, unselecting "Validate module definitions", or via the API using the "ignoreChecks" boolean.