Community
Participate
Working Groups
For example, I ran this on 'org.eclipse.equinox.p2.artifact.repository', the proposed list of unused dependencies was: org.eclipse.equinox.app org.eclipse.equinox.internal.provisional.p2.metadata org.eclipse.equinox.p2.repository.spi org.eclipse.osgi.framework.log org.osgi.service.prefs After removing them all, in order to fix resulting compilation errors, 2 packages needed to be added back: org.osgi.service.prefs org.eclipse.equinox.p2.repository.spi
Dupe of bug 99031, bug 181074 of bug 238694?
I have once again given an attempt at this functionality, and once again the story is pain and sorrow. This is very unfortunate because this bug makes the overall functionality useless for any serious development. I do not claim that I would do better, but I think that we should not leave this functionality enabled by default since we know that it is broken in some fundamental ways and can only cause frustration.
Created attachment 163405 [details] map files of the p2 projects Find attached a map file of all the p2 projects in a state where running a "find unused dependency" will result in a compile errors.
I think in our case this is a duplicate of bug 181074. Whenever I have tried this on p2 bundles, it always produces the wrong result due to our extensive use of import-package. We should likely just disable this functionality for any bundle that has import-package if it can't be fixed.
See also bug 208844 for the same problem in the manifest cleanup wizard. *** This bug has been marked as a duplicate of bug 181074 ***