Oxygen XML Forum

We develop add-ons and have been launching oxygen with the following system properties (paths made up for demonstration):

-Djava.compiler=NONE -Xss512k -Xmx256m -XX:SoftRefLRUPolicyMSPerMB=10 -XX:PermSize=128M -XX:MaxPermSize=256M
-Dcom.oxygenxml.app.descriptor=ro.sync.exml.AuthorFrameDescriptor
-Dcom.oxygenxml.editor.frameworks.url="file:///C:/path/to/frameworks"
-Dcom.oxygenxml.additional.classpath="C:/workspace/projectA/target/classes;C:/workspace/projectB/target/classes"

Recently we have updated to oxygen 18.1 and com.oxygenxml.editor.frameworks.url is no longer being picked up, oxygen is always pointing to default frameworks directory. The other system properties we set are working, however (com.oxygenxml.additional.classpath, etc). I have been scratching my head over this, and tried a few different configuration variations, but to no avail.

Any thoughts as to why this would start happening in 18.1?

Hi,

Indeed the "com.oxygenxml.editor.frameworks.url" system property does not work in version 18.1. We have registered this problem and we will let you know when it will be fixed.

What you can do for now is to create a plugin that sets the "Custom frameworks directory" option (from Document Type Association / Locations options page).
Here you can read more about "Plugins for the Standalone Distribution":
https://oxygenxml.com/oxygen_sdk/oxygen ... ugins.html

The API that you can use to impose global options is: Here is the javadoc for this API:
https://www.oxygenxml.com/InstData/Edit ... ng.Object-
There are two different keys that must be set:

• one for using custom frameworks directory (it correspinds to a boolean value, so you must set the "true" value):

  Code: Select all

  ro.sync.exml.options.APIAccessibleOptionTags.USE_CUSTOM_FRAMEWORKS_DIRECTORY_URL

• one for custom frameworks directory URL:

  Code: Select all

  ro.sync.exml.options.APIAccessibleOptionTags.FRAMEWORKS_DIRECTORY_URL

Please let us know if you need more information.

Best regards,
Mihaela

Thanks Michael. Currently we are manually setting the frameworks location in the application which points to our development frameworks which works for the time being. Any idea when a fix might be released?

Hi,

We will try to make the fix available in the next maintenance build for 18.1 (a month from now).
We will let you know when it will be released.

Best Regards,
Mihaela

Ok thanks again, Mihaela.

Hello,

Just to update the thread this problem has been resolved in the latest maintenance build of Oxygen 18.1, 2016112217 (released on November 28th):

System properties: The system property com.oxygenxml.editor.frameworks.url no longer worked to specify the frameworks location

You can download it from our web site:
http://www.oxygenxml.com/download.html

The list of bug-fixes can be found here:
http://www.oxygenxml.com/build_history.html#2016112217

You can follow the release/build RSS feed here:
http://www.oxygenxml.com/rssBuildID.xml

Let us know if you encounter further problems with this new build.

Regards,
Ionela

Yes I can confirm that it is now working for us. Thanks again!