Community
Participate
Working Groups
3.6 RC3 After doing a "Compare With > API Baseline..." operation I was seeing all sorts of misleading API changes between 3.6 and 3.5 bundles. It turned out that I had auto-build off. There were associated exceptions in the log that I had not noticed. We should ensure the workspace is built before doing the compare since the tooling relies on it. The exceptions in the log were as follows, but the compare operation did not report any problems. org.eclipse.core.internal.resources.ResourceException: Resource '/org.eclipse.debug.core/bin' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:326) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:200) at org.eclipse.core.internal.resources.Container.members(Container.java:265) at org.eclipse.core.internal.resources.Container.members(Container.java:248) at org.eclipse.pde.api.tools.internal.model.ProjectTypeContainer.doVisit(ProjectTypeContainer.java:124) at org.eclipse.pde.api.tools.internal.model.ProjectTypeContainer.accept(ProjectTypeContainer.java:95) at org.eclipse.pde.api.tools.internal.provisional.comparator.ApiComparator.internalCompare(ApiComparator.java:1058) at org.eclipse.pde.api.tools.internal.provisional.comparator.ApiComparator.compare(ApiComparator.java:374) at org.eclipse.pde.api.tools.internal.provisional.comparator.ApiComparator.compare(ApiComparator.java:402) at org.eclipse.pde.api.tools.internal.provisional.comparator.CompareApiScopeVisitor.visit(CompareApiScopeVisitor.java:107) at org.eclipse.pde.api.tools.internal.provisional.comparator.ApiScope.accept(ApiScope.java:71) at org.eclipse.pde.api.tools.internal.provisional.comparator.ApiComparator.compare(ApiComparator.java:657) at org.eclipse.pde.api.tools.ui.internal.wizards.CompareOperation.run(CompareOperation.java:82) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
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.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
