Community
Participate
Working Groups
From what I can see, all the individual bundles from master-equinox are contained in manifest and (other) feature.xml file. I don't think we need them in 'master-equinox' feature. This is similar to bug 426634. I'll try a test build first, but think this are here simply for PDE based builds, where we may have to used this technique to control the order that things were compiled in. But, I think Tycho/Maven handles that pretty well. <plugin id="org.eclipse.equinox.supplement" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.eclipse.equinox.http.registry" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.eclipse.equinox.http.jetty" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.eclipse.equinox.http.servlet" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.eclipse.equinox.http.servletbridge" download-size="0" install-size="0" version="0.0.0" unpack="false"/> <plugin id="org.eclipse.equinox.servletbridge" download-size="0" install-size="0" version="0.0.0" unpack="false"/>
Again, test build seemed fine ... so committed for Saturday N-build. Assuming that build looks ok, that leaves only 4 features in equinox master: id="org.eclipse.equinox.sdk" id="org.eclipse.osgi.compatibility.plugins.feature" id="org.eclipse.equinox.weaving.sdk" id="org.eclipse.equinox.starterkit.product.feature" I'll wait to play with those until later.