Community
Participate
Working Groups
Build 20020624 When you hit OK on a project's property page, the autobuild runs for all projects. If there are errors in External Tool Builders for other projects, this can cause a dialog to pop up telling the user that the build has failed, even if the current project built sucessfully. To reproduce (a particularly annoying case): 1) Create 2 java projects - Foo and Bar 2) From Foo's External Tool Builders property page, create a new builder that is pointed to the .project file. Exit the page, and click OK when the error dialog opens (.project is not a working External Tool) 3) Open the properties page for Bar and hit OK immediately. 4) The same error dialog opens complaining about an External Tool Internal Error (for Foo), even though Bar has no External Tool builder defined. Closing the project properties window should only rebuild the current project.
Did you make a change on the project properties page? If not, no build should occur.
You do not need to make a change to Bar's property page for it to complain about the broken External Tool builder. There are 2 problems here: 1) The external tool builders are running when there are no changes made to the property page. 2) The external tool builders for other projects are running when changes are made to a project's property page.
External Tools issue.
Waiting for Core to provide support on this.
Needs investigation.
My understanding of the problem here is that the core runs a build whenever files are changed in the workspace. Editing the project builders writes data to the .project file and now to the .externalToolBuilders directory.
Adam's problem #2 is covered by bug 21029. However, this doesn't alter the fact that no changes should happen if the user does not modify anything in the properties page (Adam's problem #1).
The BuilderPropertyPage nows does verification on ok to check that anything has changed. Please verify (Jared).
Verified code.
