Oxygen XML Forum

Hello,

We are currently using OxygenXML 25.0.
We have multiple custom plugins for OxygenXML Editor where we placed our custom plugin related shared library .jar files in a new folder (/custompluginlib) instead of /lib
(as per topic21486.html which will have "Additional libraries present" if custom libraries were added to /lib)
and added the <runtime>/<library path="${oxygenInstallDir}/<path to jar file>" scope="global"> entries in each of our plugin's plugin.xml file.

We are trying to upgrade to the latest OxygenXML version 27.0 but we encountered an issue upon startup where our plugins prompted several errors.
We tried running oxygen.bat to check the console for java errors and found the error below for each of the jar files
---
ERROR [main] ro.sync.exml.plugin.PluginManager - Skip loading in class loader resource located outside of the plugin folder <path to jar file>
---
We tried putting the custom plugin lib folder (/custompluginlib) in the /plugins folder but same error was prompted (also tried relative folder notations (..) but of course it was not allowed)
and could only resolve the issue when placing it in each of the actual plugin folder (e.g. /plugins/<pluginname>/custompluginlib)
This resolution though is not good as it requires several copies of the same .jar files in multiple plugins and will increase the size and not good maintenance-wise as would need to update multiple locations when a jar file needs to be updated.

Kindly advise if there is a way to allow a "shared custom plugin library folder" for our custom plugins. Thanks

From OxygenXML Support
----
For security reasons, since Oxygen 26, plugins have been disallowed by
default from loading resources outside the plugin directory.

There is a Java system property which can be set in the startup script
to skip these checks:
-Dcom.oxygenxml.plugins.skip.check.resources.location=true

You can probably skip this check by setting in the plugin.xml this property:
<property name="com.oxygenxml.plugins.skip.check.resources.location" value="true"/>
----

Used the plugin property instead and it works. Thanks