Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] Eclipse EGit updates site down ?

On 13 May 2010, at 00:48, Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx> wrote:

On 12 May 2010, at 23:50, Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx> wrote:

2010/5/13 Shawn O. Pearce <spearce@xxxxxxxxxxx>
Steven Van Poeck <svanpoeck@xxxxxxxxx> wrote:
> Please point me to the correct mailing list if this is out of topic.
> I'm trying to install EGit since about a week using
> but it systematically returns:
> "Network connection problems encountered during search.
>  Unable to access "".
>    Error parsing site stream. [The XML stream is not a valid default
> "site.xml" file. The root tag is not site.]

Huh, our EGit update sites no longer have a site.xml file, and are
instead returning an HTML error page with "404 Not Found" message
on them.

Chris, any idea what's going on?

I checked our download site using Eclipse Provisioning Admin UI and this finds all the
p2 metadata it expects so it doesn't look broken from p2 perspective (don't know what this tool
covers in detail). 

I downloaded Zend Studio and will try to reproduce Steven's problem.
I installed Zend Studio 7.2 and then installed egit 0.7.1 from
via "Help > Install new software" and everything worked as expected (see attached screenshot).

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