|Re: [egit-dev] Eclipse EGit updates site down ?|
On 13 May 2010, at 00:48, Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx> wrote:
Note that this will only work if using P2. The old update manager uses site.xml, whereas P2 looks for artifacts.jar.
It is possible to configure, in 3.4, whether P2 is used or not as follows. I believe you will be able to recreate the problem by enabling the "classic update" option, which will then make it look for site.xml (and fail).
Is there any reason we don't publish a site.xml file as well to enable this case? There are those who thought (particularly earlier releases) that P2 wasn't stable enough for general use and will have disabled it.
Interaction with legacy Update Manager
In Eclipse platform version 3.4, the old Update Manager still exists under the covers for backwards compatibility. You can even re-enable the old Update user interface by enabling the "Classic Update" capability on the General > Capabilities preference page.
Back to the top