Community
Participate
Working Groups
After I upgrade to a new integration build, I always end up with build errors on binary plugins. Performing a single Rebuild All does not fix the problem. I must perform several Rebuild Alls to clear all the errors. Here's typically what I do when updating to a new integration build: 1) Rename my old eclipse directory 2) unzip the new integration build to the same location as the old one 3) unzip the org.eclipse.releng.tools and the org.eclipse.pde.junit plugins into the drop (available from respective team's websites). 4) start new eclipse on my old workspace 5) perform an Import on all binary projects choosing to use linked resources (I have the org.eclipse.team.* projects as source and others as binary) 6) Perform a Rebuild All After these steps, several binary plugins have red Xs and cannot be built. Because of this, the team projects do not build either. Performing a Rebuild All seems to fix 1 of the errors at a time. Eventually, I get ride of all the errors and can continue working.
This seems like a compiler problem, not a PDE problem. During the import, PDE sets the classpath and let the JDT builders do the rest. Your problem seems to go away when you rebuild one project at a time. If PDE made an error in classpath computation, no amount of rebuilds in the world could fix the problem. Moving to JDT core for comment.
Closing. We don't believe this reproduceable... not even on 2.1.
