DO NOT REPLY [Bug 46203] input task can lose data
https://issues.apache.org/bugzilla/show_bug.cgi?id=46203 J.M. (Martijn) Kruithof j...@apache.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Comment #3 from J.M. (Martijn) Kruithof j...@apache.org 2009-02-07 11:12:44 PST --- I'd suggest to do use one of the following methods: 1) Use an input file per exec task 2) Use inputstring in combination with properties As there may be tasks, unknown to us, using standard in, there is nothing we can do to fix this issue. (If this were not the case we could have wrapped standard in somehow and used that everywhere instead, this does not seem to be a viable path.) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
DO NOT REPLY [Bug 46203] input task can lose data
https://issues.apache.org/bugzilla/show_bug.cgi?id=46203 --- Comment #1 from Stefan Bodewig [EMAIL PROTECTED] 2008-11-14 03:57:31 PST --- actually, things are a lot worse - and a lot more difficult to fix. Throw in an exec task and all bets are off http://ant.apache.org/faq.html#input-makes-exec-hang There is a recommended way for reading an input's tasks input from a file and that is to use a different InputHandler. Your customer shouldn't use stdin redirects at all, this is not a supported use-case for input (and thus I could simply claim it is a bug). What you should use is a properties file with the answers to your different input tasks (the keys of that property files are the input's prompts) and a PropertyFileInputHandler. I know you said you may not be able to change things on your side, but this is at least as much a you are using ant in a way that it doesn't support as a bug. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
