Static plugins allow you to load files and code into your dotCMS installation so that they are used in addition to, or in place of, the core dotCMS installation files. Static plugins allow you to customize both dotCMS configuration and code without modifying the core dotCMS installation or code files. This enables you to add and modify configuration and custom logic without inhibiting your ability to upgrade to new versions.
Static Plugins are not designed for docker
Static plugins allow for:
- Configuration files to be replaced.
- Specific values in key configuration files to be added or replaced.
- Any dotCMS file to be overwritten.
- New files to be deployed.
- Overriding core dotCMS Java classes to modify and extend dotCMS functionality.
One of the most common uses of Static Plugins is to override the default dotCMS configuration. For example when you set a property in a plugin dotCMS will use your value for that property even if the value is set in the dotCMS core files. This is also true for Java code. Your plugin Java code will come first in the classloader which means that if your plugin provides the same classes as dotCMS your classes will be picked up first. This provides great power and flexibility.