Migrate the update site to the p2 repository format

[jplandrain]

The newer p2 repository format gives a better integration with other Eclipse tools like Yoxos. Please, migrate the update site to the p2 format.

Getting started: http://wiki.eclipse.org/Equinox/p2/Getting_Started_for_Releng
Further reference: http://wiki.eclipse.org/Equinox/p2

[mchr3k]

Can you clarify what you mean by "better integration"? What can a p2 repository do which my current repository cannot do?

[jplandrain]

As I said, integration with Yoxos, i.e. one of the popular Eclipse provisioning tools: https://yoxos.eclipsesource.com/

It also concerns the integration/coexistence with other plugins, and the future deprecation of the update manager that has already been started in Eclipse 4.2 (you can still install update manager plugins in 4.2, but with a poor integration into the target environment). Please, read https://bugs.eclipse.org/bugs/show_bug.cgi?id=311590

[mchr3k]

Does Yoxos work at all with my update site or does it require the newer format?

[jplandrain]

Yoxos requires the equinox p2 format. No, it can't work with the current update site, hence the current feature request: we use Yoxos Enterprise in the European Parliament and I would like to distribute your version of the jd-eclipse plugin to our developers (your version is much better than the original one in our local environment).

[mchr3k]

Ok I'll take a look at switching my update site format. I should have some time in the next few weeks.

I'm glad you find my plugin useful :) How many developers are you expecting to deploy this to? I'm always interested to hear about how my plugins get used in the wild.

[jplandrain]

Thank you. That doesn't look too difficult (hopefully): http://eclipsesource.com/blogs/2009/06/04/who-writes-your-metadata-me-i-use-a-publisher/
I can help to test the result.

We don't have the exact number of developers (it changes too frequently), but it's roughly estimated around 200.

[mchr3k]

I'm really keen to do this but the conversion is less trivial than I hoped. I like the old update site format because it doesn't require a build step - I can just write a site.xml file and then put files in a particular directory structure.

I'm definitely still in favour of doing this conversion but I'm not sure when I'll have time to puzzle it out. If you think you know how to do this then feel free to submit a pull request.

[esimioni]

Before opening a new issue, would that migration make the update site work with Kepler? Currently it doesn't work.

[mchr3k]

@esimioni I just tested my update site in Kepler and it worked. What was your problem?

[mchr3k]

@jplandrain I took another look at this again this evening and hit a NPE in some of the Eclipse tooling when trying to upgrade the update site. I am still keen to do this upgrade - I'm sorry this is taking quite so long!