Open slopjong opened 12 years ago
It should be enough to read the feature file. All the plugins are listed there and can be assembled to a download link.
The site.xml is there for backwards compatibility. The artifacts and content files should be considered if the site.xml doesn't exist.
See http://stackoverflow.com/questions/9783468/generate-site-xml-from-existing-update-site http://wiki.eclipse.org/Equinox/p2/p2_index
It looks like eclipse update sites can be a whole mess. The tool will assume that a site.xml exists and won't fiddle with p2 repositories. Maybe a later version will support p2.
http://eclipsesource.com/blogs/2012/06/05/understanding-the-p2-index-file/ http://eclipsesource.com/blogs/2012/06/11/creating-p2-composite-repositories-on-the-command-line/
http://example.com/update-site/p2.index http://example.com/update-site/content.xml http://example.com/update-site/content.jar http://example.com/update-site/compositeContent.xml http://example.com/update-site/compositeContent.jar http://example.com/update-site/artifacts.xml http://example.com/update-site/artifacts.jar http://example.com/update-site/compositeArtifacts.xml http://example.com/update-site/compositeArtifacts.jar http://example.com/update-site/site.xml
The most important resources seem to be the content.xml/jar , artifacts.xml/jar and site.xml.