Community
Participate
Working Groups
Build: RC1 Import org.eclipse.jdt.debug.ui as binary. You will see that its plugin.xml has warnings. Since manifest files must not be validated in binary projects, and since I recall seeing commments in our code that say: "if it's binary, then skip validation" or words to that effect, this might simply imply that the check if a project is binary is returning false when it's actually true.
This only happens if the project is imported as binary without linking. The test for binary plug-in project is flawed in that it expects to find BinaryRepositoryProvider. We only use this provider for linked binary projects: String binary = project.getPersistentProperty (PDECore.EXTERNAL_PROJECT_PROPERTY); if (binary != null) { RepositoryProvider provider = RepositoryProvider.getProvider(project); return provider instanceof BinaryRepositoryProvider; } The fix is to allow the provider to be null (local binary project).
Can this be contributing to bug 66228 as well? I have the whole SDK (except for our own plugins) as binary projects. Is this fixed for i200406082000?
This bug was certainly contributing to the overall problem, but has been fixed in builds from yesterday. There are other remaining issues with the builder.