Community
Participate
Working Groups
Apologies if this is a dupe. Steps to repro: (See bug 230806.) Instead, we ought to prepopulate p2 w/ the Ganymede update site, as we did for the Europa site last year.
I agree with the idea but don't think this is a p2 issue. it is more of an EPP thing no?
*** This bug has been marked as a duplicate of bug 224278 ***
(In reply to comment #1) > I agree with the idea but don't think this is a p2 issue. it is more of an EPP > thing no? No, it's a platform thing, but p2 needs to enable it. Couldn't one of the platform features (if not p2 itself) just contribute a <discovery> URL, presumably as was done for Europa? (See also bug 230323.)
The org.eclipse.sdk feature provides the Ganymede discovery URL. The problem is we never actually parse feature.xml files for things that are already installed, so this needs to happen at build time.
(In reply to comment #4) > The org.eclipse.sdk feature provides the Ganymede discovery URL. The problem is > we never actually parse feature.xml files for things that are already > installed, so this needs to happen at build time. Sure you do... when I install EMF, I get the EMF <update> site listed -- or is the platform considered "already installed" but EMF is considered "freshly installed?" I don't, however, get any <discovery> sites listed by default, but that's bug 230323. What if there was a new attribute on the <discovery> node for "always on" or "enabled by default" ? The the Ganymede site could be turned on magically OOTB, but others would need to be "discovered" in the Manage Sites dialog and manually enabled... ?
When you unzip things into dropins or plugins, we parse the feature during the install process, so we have a chance to load the discovery and update site URLs. For feature that are "pre-installed", we never parse the feature.xml files (in fact we don't even know/care if the feature.xml files are present - we only include them for backwards compatibility). We could of course do an extra parse of all feature.xml files at some point to discover the discovery/update sites, but this adds extra startup cost.
(In reply to comment #6) > We could of course do an > extra parse of all feature.xml files at some point to discover the > discovery/update sites, but this adds extra startup cost. How about a "Discover" button on the UI? Or make the "Refresh" button search pre-installed features too?
