Community
Participate
Working Groups
I created a new workspace, set my API baseline to 3.5.0, and then checked out the platform-ui projects. After the checkout, during the initial build of the workspace, I get the following exceptions: null Error Fri Feb 05 15:00:14 EST 2010 Error logged from API Tools Core: org.eclipse.core.internal.resources.ResourceException: Resource '/org.eclipse.ui.workbench.compatibility/bin' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:330) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:204) at org.eclipse.core.internal.resources.Container.members(Container.java:179) at org.eclipse.core.internal.resources.Container.members(Container.java:164) 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:1120) 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.builder.BaseApiAnalyzer.checkCompatibility(BaseApiAnalyzer.java:1083) at org.eclipse.pde.api.tools.internal.builder.BaseApiAnalyzer.analyzeComponent(BaseApiAnalyzer.java:243) at org.eclipse.pde.api.tools.internal.builder.ApiAnalysisBuilder.buildAll(ApiAnalysisBuilder.java:456) at org.eclipse.pde.api.tools.internal.builder.ApiAnalysisBuilder.build(ApiAnalysisBuilder.java:250) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
That's on this week's I build, I20100202-0800 PW
*** Bug 305333 has been marked as a duplicate of this bug. ***
Looking at our code and the trace, this is happening because the output location does not exist. We find the output locations to visit from the bundle classpath, and naively assume they exist (which they should). Our builder already has support to abort if there are classpath errors, so in this case I would expect the output locations to be fine. The other case could be that the Java builder ran but did not produce any class files, although I am not sure when this could occur. Olivier, are the cases where the Java builder can run and not produce any class files?
If there are no class files, then we should have JDT errors. I wonder if the java builder did run in this case.
I can produce an identical trace if I disable the Java builder for the project: org.eclipse.core.internal.resources.ResourceException: Resource '/org.eclipse.ui.workbench.compatibility/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:1057) 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.builder.BaseApiAnalyzer.checkCompatibility(BaseApiAnalyzer.java:1118) at org.eclipse.pde.api.tools.internal.builder.BaseApiAnalyzer.analyzeComponent(BaseApiAnalyzer.java:238) at org.eclipse.pde.api.tools.internal.builder.ApiAnalysisBuilder.buildAll(ApiAnalysisBuilder.java:474) at org.eclipse.pde.api.tools.internal.builder.ApiAnalysisBuilder.build(ApiAnalysisBuilder.java:309) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) This would mean that either the Java builder did not run at all, or we somehow ran before the Java builder.
(In reply to comment #5) > > This would mean that either the Java builder did not run at all, or we somehow > ran before the Java builder. Maybe a timing problem ... I can confirm that I didn't disable the java builder :-) PW
marking this as a dupe of bug 303214, as the case where a required bundle has not been built appears to be causing this as well. Each time I reproduce this there is no bin folder in the project (meaning the Java has not run). *** This bug has been marked as a duplicate of bug 303214 ***
