Community
Participate
Working Groups
At least, in my humble opinion. This was first discussed in bug 358789 comment 1 but I believe fell through the cracks. The platform feature (not SDK) is what is usually used to construct EPP packages (and probably other products) and seems clear the e4 incubation repo should not be there, built in. Currently, the repos showing up, by default, in EPP JEE (near M4) package is e4 0.11 Updates http://download.eclipse.org/e4/updates/0.12 Juno http://download.eclipse.org/releases/juno Mylyn for Eclipse Juno http://download.eclipse.org/mylyn/releases/juno The Eclipse Project Updates http://download.eclipse.org/eclipse/updates/4.2 The Eclipse Web Tools Platform (WTP) software repository http://download.eclipse.org/webtools/repository/juno FYI, I think eclipse updates, http://download.eclipse.org/eclipse/updates/4.2 in the list, should stay. In bug 358789 there as talk of it being redundant, but it is not, exactly. There are potential scenarios where, the platform might need to put in a "quick emergency fix" in their updates/4.2 repo that would not be reflected in the content meta data of /releases/juno. (Plus, I think users would "feel better" seeing it there, just so they know for sure it is included). The other "extra" ones, Mylyn and WTP, were consciously put in EPP package, since they are "well known" for releases fixes or fix packs "off cycle" (unlike EMF, GEF, or DTP which are not known for doing this). I should say, I _assume_ these are coming from the platform repo itself, via some p2.inf files, or similar ... I do not see them mentioned in the feature.xml files.
to be honest, I can't say this is "causing a problem", just "looks wrong" (and, is, slightly wrong :) since the platform does not include anything from e4 repo, its just like "advertising" it, inappropriately, so will mark it "minor".
*** Bug 366655 has been marked as a duplicate of this bug. ***
Created attachment 210618 [details] Patch
Released.
