Summary: | [ExternalTools] Project properties runs autobuild for all projects | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Adam Schlegel <Adam_Schlegel> |
Component: | Ant | Assignee: | Jared Burns <jared_burns> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | CC: | jverhaeg |
Version: | 2.0 | Keywords: | ui |
Target Milestone: | 2.1 M4 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Adam Schlegel
2002-06-24 16:44:12 EDT
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. |