Community
Participate
Working Groups
The site references have recently gone missing from the Galileo metadata repository. This is an entry in the content.xml that looks like this: <references size='58'> <repository url='http://download.eclipse.org/stp/updates/' type='0' options='0'/> ... </references> These were present until fairly recently (resulted in a big list of disabled sites in the Available Software Sites preference page). These references are added at metadata generation / publish time. I'm not sure what changed to cause these to disappear. I noticed they are still present in newly generated Eclipse project metadata repositories, so it seems related to the Bucky builder changes.
Thomas, Do you agree this is an issue with the builder? I do know these sites are missing in the EPP builds, but not sure if related. See bug 275520.
The builder currently only mirrors the needed UI's from the contributed repositories so it never builds a <references> element. What should the element contain? a) The sum of all <references> in the mirrored repositories b) The list of mirrored repositories c) Both ?
(In reply to comment #2) > The builder currently only mirrors the needed UI's from the contributed > repositories so it never builds a <references> element. What should the element > contain? > > a) The sum of all <references> in the mirrored repositories > b) The list of mirrored repositories > c) Both > > ? > I think only 'a'. While it might work out in the end, with enough attention paid, we often "contribute" to Galileo with some 'interim' site, and our features reference the 'final' site that will be valid after release. If I understand what you are asking.
Awaiting resolution of bug 275800
For Eclipse contents at least, the list of Repositories is also in the feature.xml / url / discoverySite attribute ... I have some understanding why p2 doesn't expose this property by default any more - I assume that's in order to support corporate mirrors where direct access to eclipse.org is not desired, see bug 275800 comment 2. But for Galileo, would it be an option to generate the siteReferences on the final Galileo site by reading the feature.xml contents? Or would such a generation step other meta-info that should really be taken from contributing repos?
I would make life much easier if each contribution could make their references end up in the <references> element. Perhaps the site generator takes care of this already? Scanning feature artifacts to find meta-data doesn't sound too appealing. It implies a rewrite of the builder since it relies 100% on meta-data until it's time to do the actual (optional) mirroring. Accessing artifacts to build meta-data would slow down the build significantly.
The site references are already generated from the feature.xml at metadata generation time. The only problem here AFAIK is that the Galileo build now works by mirroring the p2 repositories generated by the different projects, and there is no support yet for mirroring repository references.
*** This bug has been marked as a duplicate of bug 280024 ***
