Community
Participate
Working Groups
Run API Use Scan report Put "org\.eclipse\.pde\..*" in Search in And Search For. Check Error log - lots of error like org.eclipse.core.runtime.CoreException: Unable to resolve superclass org.eclipse.pde.ui.templates.OptionTemplateSection for org.eclipse.pde.internal.ui.templates.PDETemplateSection at org.eclipse.pde.api.tools.internal.model.ApiType.getSuperclass(ApiType.java:326) at org.eclipse.pde.api.tools.internal.builder.Reference.resolveSuperTypeMethod(Reference.java:466) at org.eclipse.pde.api.tools.internal.builder.Reference.resolveVirtualMethod(Reference.java:415) at org.eclipse.pde.api.tools.internal.builder.Reference.resolveSuperTypeMethod(Reference.java:468) at org.eclipse.pde.api.tools.internal.builder.Reference.resolveVirtualMethod(Reference.java:415) at org.eclipse.pde.api.tools.internal.builder.Reference.resolve(Reference.java:335) at org.eclipse.pde.api.tools.internal.builder.ReferenceResolver.resolveReferenceSets(ReferenceResolver.java:105) at org.eclipse.pde.api.tools.internal.builder.ReferenceResolver.resolveReferences(ReferenceResolver.java:76) at org.eclipse.pde.api.tools.internal.provisional.search.ApiSearchEngine.getResolvedReferences(ApiSearchEngine.java:167) at org.eclipse.pde.api.tools.internal.provisional.search.ApiSearchEngine$ReferenceExtractor.visit(ApiSearchEngine.java:104) at org.eclipse.pde.api.tools.internal.model.ArchiveApiTypeContainer.accept(ArchiveApiTypeContainer.java:206) at org.eclipse.pde.api.tools.internal.model.AbstractApiTypeContainer.accept(AbstractApiTypeContainer.java:62) at org.eclipse.pde.api.tools.internal.model.Component.accept(Component.java:67) at org.eclipse.pde.api.tools.internal.provisional.search.ApiSearchEngine.searchReferences(ApiSearchEngine.java:246) at org.eclipse.pde.api.tools.internal.provisional.search.ApiSearchEngine.search(ApiSearchEngine.java:313) at org.eclipse.pde.api.tools.ui.internal.use.ApiUseScanJob.run(ApiUseScanJob.java:156) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.