_Uninstalling a module

Uninstalling a module involves removing the module JAR from /WEB-INF/lib folder and restarting Magnolia. However, this is rarely enough as modules add new configuration nodes and modify existing configuration during their installation. The use of a module also results in changes to content repositories. Removing all of this information is difficult without knowing exactly what the installation tasks were.

If you want test a given module, use the embedded Derby database and take a backup of your repositories folder. Then install the module and try it out. When you are done testing, remove the module JAR and restore the repositories folder from the backup. This way you can go back to square one after the trial. We also recommend that you implement segregated development and production environments and take regular backups for disaster recovery so you can revert to a prior state in a routine fashion.