Community
Participate
Working Groups
For a XML to HTML course content system, I've set up an Ant configuration like this: Buildfile: ${workspace_loc:/sce/courses/}/build.xml Arguments: ${string_prompt:Build type} ...as my system has a directory of build scripts (mainly ant & XSLT), and many courses, each with their own build file, like this (simplified for clarity): sce * build-tools * courses * course-a * build.xml * (course files) * course-b * build.xml * (course files) This works (allowing me to choose course-a or course-b, and the build runs), but the folder_prompt dialog is shown twice when running (folder_prompt, string_prompt, then folder_prompt again), and multiple times when editing the configuration. The folder_prompt ("Please input a value for workspace_loc") is shown 11 times just from clicking "External tools configurations" before showing the configuration dialog. Each switch between configuration tabs provokes at least one more folder_prompt, which makes me supect that it is generating the variable value for each tab, rather than once for each dialog. Also present in Eclipse 3.7.2 on Ubuntu 12.04
Can you attach a buildfile that produces the problem (or a complete test project)? If I had to take a guess, when we are resolving the buildfile we are actually invoking any variables, which would cause the multiple prompting.
Created attachment 222721 [details] ant-based XSLT processing example project I'm afraid my build system is a bit of a tangle, with builds calling builds. Attached is a zip of the build scrips, and a test course - configure/run courses/XMLguide/build.xml
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. -- The automated Eclipse Genie.
Nothing has changed.
