Resources Importer

Set this to "true" to enable the Resources Importer Developer Mode for a
theme plugin. The developer mode requires the "resources-importer-web"
plugin, which resides in the Resources Importer CE/EE app. The Resources
Importer CE/EE app can be downloaded from Liferay Marketplace.

The "resources-importer-web" plugin allows front-end developers to package
layouts, portlet configurations, site pages, and web content together in a
theme without saving it as a compiled LAR file. This allows for greater
flexibility in the plugin's usage between Liferay Portal versions. When a
theme has the developer mode turned on, layouts and resources of the site
template are deleted and recreated during new deployment. This allows for
modifications to show without manual deletion of site templates.

For marketplace themes, the "resources-importer-web" must be included in
the "required-deployment-contexts" list. Also, the
"docroot/WEB-INF/src/resources-importer" folder must exist within the
theme structure. Failing to comply with these settings will cause an error
preventing submission of the theme.

Security Manager

Set to "true" to enable the Security Manager. If the plugin is being
distributed either through Liferay Marketplace or through a web site, it
must be turned on. Also, the security manager should be turned on when
doing final testing on applications, due to the assumption that
potential users will also have the security manager turned on.

As a suggested plugin development approach, disable the security manager
(by setting this property to false) until plugin development is complete.

Specify whether to allow the plugin's servlet filter hooks. Setting this
to "true" gives the plugin permission to pre-process requests going to the
portal's servlets and post-process requests coming from the portal's
servlets.

By default, the plugin's servlet filter hooks are not allowed.

Examples:

security-manager-hook-servlet-filters-enabled=false

Specify struts action paths that the hook plugin is permitted to add or
override.

JNDI Security

Specify which services the plugin can look up. Use regular expressions to
make this dynamic.

Example:

Using the sample values below, the plugin can look up objects for key
names matthew, mark, Mark, luke, and Luke. In addition, the plugin can
look-up objects for key names containing john with zero or more characters
preceding and/or trailing john.