you may want to try using maven 2 with a plugin for this sort of thing. it sounds to me like a plugin for exactly this sort of thing should already exist. if not, you could create a maven plugin yourself. there's instructions and documentation on the apache maven website for how to do this. i should warn you that, having made a couple maven plugins myself, you should be prepared to spend at least 5 or 6 hours learning how to write the plugin, and then actually writing it. alternatively, if you're using ant, you could write an ant task to do the same job, or plugin for whichever other build system you may be using.


i host my update site at eclipse labs using git. this way to release, i just perform the following steps:

  • select the feature project and export as deployable features
  • commit and push the update site project


i have voted up zvikico's response but wanted to add that you really don't want to create a site.xml anymore. the site.xml does not have the in-depth plugin/package requirement information that the content.xml has. modern eclipse's support both the new (content.xml/artifacts.xml) and old (site.xml) style metadata, but the new style will give you more consistent provisioning.


what you need is to do a "pde build". google the term and you'll find plenty of information, guides, articles and what not. start with the eclipse built-in help, under plugin development environment guide -> tasks you will find the basic articles that will get you started.

afaik, there is one small catch. the current release can generate all the p2 metadata that you need but not a proper site.xml. this is the simplest issue, it can be easily generated with a simple code.

Related Query

More Query from same tag