Community
Participate
Working Groups
I switched from 0.137 to 0.202 using my [old] workspace. Each time after building I get the followin dialog (no log): Save Problems Reason: Errors during build. Details: Error instantiating builder: org.eclipse.pde.ManifestBuilder Error instantiating builder: org.eclipse.pde.SchemaBuilder Error instantiating builder: org.eclipse.pde.ManifestBuilder Error instantiating builder: org.eclipse.pde.SchemaBuilder Error instantiating builder: org.eclipse.pde.ManifestBuilder Error instantiating builder: org.eclipse.pde.SchemaBuilder I guess the reaon is that 0.202 does not include PDE. The platform should not call builders of which the plug-in is not available. If the error is not severe (it seems I can continue to work) the dialog should only be a warning dialog. NOTES:
PRODUCT VERSION: 0.202
Fixed. I now only report the error once per session. On all subsequent build attempts during that session, a single line message is printed to the log indicating what went wrong, and no exception is thrown. I think the error is sufficiently severe that the user should be notified... it means that the project is probably no longer working as expected. However, it is annoying if this message continues to interrupt the user. My fix is a compromise on these two points.
I wasn't completely satisfied with the fix so I made some more changes. Basically the builder persistent info for the old builder would have hung around forever, and it would have maintained a reference to an old tree. I now create a "fake" builder to replace the builder that couldn't be instantiated. As far as the core is concerned, this builder looks and acts like a normal builder so no special code is required. However, when this fake builder is first run, it throws an exception, and then silently logs exceptions for all future build attempts. This made the code much cleaner.
Fixed in v207
*** Bug 5649 has been marked as a duplicate of this bug. ***
