Community
Participate
Working Groups
I have a use case from a user who has 3 builders (as set up on the builders property page): a pre-Java builder the Java builder a post Java builder The setup of the project dictates that required build path components are generated by the pre-Java builder. Due to the optimization and pref for the Java builder to abort on any buildpath problems even when the pre-Java builder creates the required build path components (a source directory in this particular case but could easily be a require library etc), the Java builder build is a noop. The workaround is to turn off the Builder Build Path preference to abort on build path problems. I believe it should be considered that other builders can manipulate the state of the project such that build path errors are corrected and the short circuit (s) of JavaBuilder.isWorthBuilding() are too aggressive.
Is this the bug 58649 ? In that bug it looks like a refresh is not performed after the pre-builder. If a refresh is performed, we would see the newly create source folder as a resource & the classpath errors would go away.
The bug looks the same except the pre-builder is doing a refresh. I expect the failure with no refresh and with no refresh I would not expect the workaround would to work.
I think this is a dup of bug 58649 since it was doing a refresh too. It appears that the classpath computation is missing the generated source folder. *** This bug has been marked as a duplicate of 58649 ***
