When some project declares a .classpath entry that is created during the build, e.g. by annotation processors, the very initial attempt to build fails with Project ... is missing required source folder error.
This causes TEA Build Util to perform the 'fast recompile', without logging the firsthand problem.
Even if that 'fast recompile' step succeeds, the 'recompile 1' is performed again, which is a lot more intrusive with the PDE workspace, and seems to eventually cause subsequent build failures.
If the firsthand problem would be logged, application developers would be lead to set the optional=true flag on such classpath entries.
When some project declares a
.classpathentry that is created during the build, e.g. by annotation processors, the very initial attempt to build fails withProject ... is missing required source foldererror.This causes TEA Build Util to perform the 'fast recompile', without logging the firsthand problem.
Even if that 'fast recompile' step succeeds, the 'recompile 1' is performed again, which is a lot more intrusive with the PDE workspace, and seems to eventually cause subsequent build failures.
If the firsthand problem would be logged, application developers would be lead to set the
optional=trueflag on suchclasspathentries.