[Jay Kirby]

I mentioned this in another post, but wanted it to get addressed independently, so I’m breaking it out here:

I recently upgraded from 5.5.1 to 6.5 and imported my projects to the new workspace I created (I also imported preferences from 5.5.1). I have some ant tasks defined that I use to trigger my maven build and they periodically display the following error when run from within the IDE:

Errors during build.
Errors running builder ‘Integrated External Tool Builder’ on project ‘myproject’.
Variable references empty selection: ${project_path}

The project also has an ant builder that runs an ant task with a buildfile specified as:

${workspace_loc:${project_path}/build.xml}

and base directory of

${project_loc:}

This worked fine with 5.5.1, but now I get the error usually the first time its run and then periodically thereafter (haven’t figured the pattern yet). If I rerun the same ant task it works fine.

I’ve tried -clean, but it didn’t help.

[Loyal Water]

Have you renamed the external tool builder? If you rename an existing external tool builder that is configured to run during auto-builds, you will get the following error: Errors during build. Errors running builder “Integrated External Tool Builder” on project <PROJECT_NAME>. The builder launch configuration could not be found. The workaround is to first disable the builder for auto-builds and then rename the builder.

[Jay Kirby]

No, it wasn’t renamed. It looks like it’s running, but that the variables aren’t defined occassionally. If I do a clean on the project, it usually runs the builder fine.

[Riyad Kalla]

Malone,

Is there a chance the project isn’t focused when you try and run the builder so the workbench isn’t setting the value for those args? The reason I ask is because we don’t instrument the External Tools at all from the base Eclipse SDK, so that’s all straight Eclipse there.

[Jay Kirby]

It probably doesn’t have the focus, but that wasn’t an issue before I upgraded to the latest version. You’d think that when a builder is associated with a specific project, the variables that scope to a project should be set appropriately.

Thought about this a bit more and ended up changing the variable I used to be build_loc (or something close to that) instead of project_loc or project_path. This fixed the issue I was seeing, but it’s odd that using the project variables worked fine regardless of which file had focus in the old version, but not the newer one.

[Author]

Posts