Community
Participate
Working Groups
This is used, as the master-jetty feature was used (see bug 406746), to put things into the final repository ... but ... everything it puts there, is already included elsewhere. You can tell, included elsewhere, since everything listed in master-ecf feature is already included in eclipse.sdk distribution. There are some exceptions. It includes org.apache.commons.httpclient and org.apache.commons.httpclient.source But those are even no longer used any longer in Eclipse ... instead org.apache.httpcomponents.httpclient, 4.x being used. (And, it, and its source, is included in eclipse.sdk (and p2 features). It would be good to get rid of this master feature ... even if it takes a while to git ride of all the master features, it'd be progress to remove the obvious ones, that should take no further adjustment.
http://git.eclipse.org/c/platform/eclipse.platform.releng.git/commit/?id=37866a803b411509422e9734ba7e30bbb6865042 http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=7ac1453bf945ff0771e1ef192a47a399a1da9724
A test build of this change failed, but seemed unrelated to this change, per se, but instead to the way qualifiers are computed, combined with the fact that we remove some .... so, I'm going to try and "touch" master-equinox, and see if that alone fixes the problems. The error message was: [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.17.0:publish-products (default-publish-products) on project eclipse.platform.repository: Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.17.0:publish-products failed: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from master.feature.group 3.4.0.v20130429-0209 to master-equinox.feature.group [1.1.0.v20130428-0418]."
(In reply to comment #2) > A test build of this change failed, but seemed unrelated to this change, per > se, but instead to the way qualifiers are computed, combined with the fact > that we remove some .... so, I'm going to try and "touch" master-equinox, > and see if that alone fixes the problems. Test build with this 'touch' went fine. Besides 'master' (which, we do have to keep, at least for one case I know of, we are left with 'master-equinox and master-equinox-weaving ... we could likely "move" their contents into 'master' (at a minimum) to avoid much of the "invalid delete" operations.
mass change to 'verified', as these bugs are either routine or obviously fixed build breaks.
