Yes, it works and I think this is a good palce to put it, actually. Thank you! -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/ ----- Mail original -----
De : Oxygen XML Editor Support <support@oxygenxml.com> À : oxygen-user@oxygenxml.com Cc : Envoyé le : Jeudi 14 juin 2012 8h24 Objet : Re: [oXygen-user] Plugin needs a system property to be configured
Hi Florent,
Indeed the plugin.xml might be a good place where certain system property key=>value pairs could be set, we'll consider this an improvement request for a future version.
Right now setting the system properties on the constructor of your ro.sync.exml.plugin.Plugin should work fine. The Plugin object is instantiated before any of the associated plugin extensions.
Regards, Radu
Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 6/13/2012 6:54 PM, Florent Georges wrote:
Hi,
I am writing a plugin for oXygen. As part of that plugin, I use a third-party library that needs a system property to be set. For now, I added it to oxygen13.2.vmoptions, but this is really not user-friendly (wrt to installation). The other option I can think of is to set the property from within Java during plugin instantiation (the class extending Plugin), but I am not sure oXygen ensures this is called before everything else in the plugin.
What is the idiomatic way to set a system property (especially as part of a plugin)? It would be nice to be able to set it in the plugin.xml actually.
Regards,
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user