Page 1 of 1

Packing Oxygen into Apache Ivy

Posted: Thu Feb 23, 2012 1:06 pm
by SSC
Hello,

we´d like to include your Oxygen plugin into our build system(Apache Ant and Ivy).
I would like to know if there is a single JAR file, which can be used for Apache Ivy?
Currently I am having a huge amount of files and folders under com.oxygenxml.editor_13.2.0.v2012011017 in my Eclipse TargetPlatform.

Can you offer us these files and folders packaged in a JAR file so that our Apache Ivy system can handle it?

Regards,

Simon

Re: Packing Oxygen into Apache Ivy

Posted: Thu Feb 23, 2012 1:25 pm
by Radu
Hi Simon,

Besides the update site distribution we also provide for download a zip package (which is usually copied to the Eclipse dropins folder and unpacked):

http://www.oxygenxml.com/download_oxyge ... os=Eclipse

I'm not sure this answers your question.

Regards,
Radu

Re: Packing Oxygen into Apache Ivy

Posted: Thu Feb 23, 2012 3:05 pm
by SSC
Actually I meant one JAR file which wraps the whole functionality of the Oxygen plugin.
When you look into the plugins folder of your Eclipse installation you usually see nearly all these eclipse plugins wrapped in a JAR file.
For instance the org.eclipse.ui_3.7.0.[...].jar, when opening with a zip programm like 7-zip, contains a folder structure which is used by plugin bundles.
/icons/
/META-INF/
/org/
.api_description
.options
about.html
plugin.properties
plugin.xml

Is it possible to get such an JAR file plugin of Oxygen as well, so that Ivy could resolve the Oxygen Dependencies for our Oxygen projekts?

Re: Packing Oxygen into Apache Ivy

Posted: Thu Feb 23, 2012 3:13 pm
by Radu
Hi Simon,

I now understand what you mean, I've seen indeed other plugins packed as such. We never explored this possibility. Some of the resources in the plugin directory are accessed by our code directly as Java Files so wrapping everything in a single JAR would mean changing a lot of code on our side to access everything using class loaders. For example the plugin (and standalone distribution as well) expects a frameworks directory to exist and then navigates that directory using standard Java File support and loads all found frameworks.

Regards,
Radu