Community
Participate
Working Groups
If you rename an existing external tool builder that is configured to run during auto-builds (by clicking on the external tool builder and choosing Edit..., then changing the name and clicking OK) the external tool will be run imediately, but the information in the configuration file will not be up to date yet because you have not exited the Builders property dialog yet. As a result, you will receive the following error message (which will briefly appear on top and then fall below the builders property dialog, making it essentially inaccessible until you exit the builders dialog): Errors during build. Errors running builder "Integrated External Tool Builder" on project <PROJECT_NAME>. The builder launch configuration could not be found. Now if you clikc "Cancel" to get at the error dialog, dismiss it, then go *back* into the Builders property dialog, you will see that your external tool is now marked as being an "Invalid External Tool Builder".
Changing version to 3.1.
Another problem here is not cancelling a name change for a builder does not role back the name change (logged as bug 126665). The launch configuration page is immediately updated but the .project file build command is not updated until the properties dialog (and therefore the page) is OK'd Hackish solutions I can think of for this problem: turn off all of the auto building external tool builders while the builder property page is open...possibly a system property? have builders not be triggered for changes in the .externalToolBuilders folder
Most likely for 3.2 this is going to remain an issue and will need to be doc'd in the readme/known issues.
Added as known issue in the Eclipse readme for 3.2 Revisit in 3.3
leaving as a known issue for 3.3
i have this solution and it works, you must go to your .project file in your work space, and you can put in comment or delete this lines <buildCommand> <name>org.eclipse.ui.externaltools.ExternalToolBuilder</name> <triggers>full,incremental,</triggers> <arguments> <dictionary> <key>LaunchConfigHandle</key> <value><project>/.externalToolBuilders/org.eclipse.wst.jsdt.core.javascriptValidator.launch</value> </dictionary> </arguments> </buildCommand> and after that you can rebuild your project and it will work correctly.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
