It's all about the answers!

Ask a question

External Tools: Variables broken if project is added to SCM


Torben Knerr (41112) | asked Dec 10 '07, 6:19 p.m.
Hi all,

we are experiencing problems with the external tools settings as soon as we add a project to Jazz SCM.

For our build, we use several Ant Build configurations defined via the External Tools Dialog. Within these configurations we make use of variables, such as ${project_loc}/build.xml. This works fine until we add the project to Jazz SCM -- after adding the project to SCM we can not run the build configuration anymore: the Error Log says "The file does not exist for the external tool named myAntBuildConfig". The External Tools dialog shows the error message "External tool location does not exist". Replacing ${project_loc} with an absolute path fixes the problem, but then we can no longer use the variables.. :-/

Does anyone experience similar problems?

Thanks and best regards,
Torben

P.S.: Just re-opened defect#35745: https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=35745

One answer



permanent link
Darin Swanson (3161) | answered Dec 10 '07, 6:48 p.m.
Please see the work item 36674 which points to the Eclipse bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=210254

HTH
Darins

"torben.knerr" <torben.knerr@zuehlke-dot-com.no-spam.invalid> wrote in
message news:fjki1q$bku$1@localhost.localdomain...
Hi all,

we are experiencing problems with the external tools settings as soon
as we add a project to Jazz SCM.

For our build, we use several Ant Build configurations defined via the
External Tools Dialog. Within these configurations we make use of
variables, such as ${project_loc}/build.xml. This works fine until we
add the project to Jazz SCM -- after adding the project to SCM we can
not run the build configuration anymore: the Error Log says "The
file does not exist for the external tool named
myAntBuildConfig". The External Tools dialog shows the error
message "External tool location does not exist". Replacing
${project_loc} with an absolute path fixes the problem, but then we
can no longer use the variables.. :-/

Does anyone experience similar problems?

Thanks and best regards,
Torben

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.