Community
Participate
Working Groups
From a recent stack trace, it looks like the release train repository still has a site.xml file. This should be removed. p2 will only consult this file if content.xml was missing or failed to be read. In this case we don't want to fall back to site.xml because it will regenerate all the release train metadata at runtime which will be extremely slow.
Who says p2 doesn't have confusing error messages? :) That message "unable to read site.xml" happens not because there is a site.xml file there at the site ... it's just the last thing p2 tries ... couldn't read content.jar, couldn't read content.xml, so it tries site.xml and can't read that either, so it is "last error" to display. Please re-open if I've misunderstood ... but, this msg has been showing up for years, even when site.xml is no where to be found.
Funny coincidence, I tried installing something from Helios using Old Update Manager just today, and all I got was "Network error". So I'd assume that the Helios Repo doesn't have a site.xml - or at least not a valid one that legacy update could consume.
(In reply to comment #2) > Funny coincidence, I tried installing something from Helios using Old Update > Manager just today, and all I got was "Network error". So I'd assume that the > Helios Repo doesn't have a site.xml - or at least not a valid one that legacy > update could consume. Correct ... not even Galileo has one ... how the time flies, eh?
