Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364732 - using default input handler doesn't work
Summary: using default input handler doesn't work
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.7.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-24 11:48 EST by Sven Köhler CLA
Modified: 2019-09-09 18:24 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Köhler CLA 2011-11-24 11:48:57 EST
Build Identifier: 

The build.xml below uses the default inputhandler. When I run this build.xml and select "run in same JRE as the workspace", then it fails with an error.

However, when I do not select "run in same JRE as the workspace" (and hence the ant build is started in a separate JVM), then the build process just stalls, and the text I enter into the console view is not passed on to the external ant build process.

On the one hand, you don't seem to close STDIN of the external process (java.lang.Process.getOutputStream.close()) and you also don't actually pass the text typed into the console view on to the external process.

Please either close STDIN of the external process (such that it fails with an error when reading from STDIN) or pass on the text typed in the console view to the external ant build process. Also, I wonder whether the text typed into the console view can be passed on to the ant build process in case the "run in same JRE as the workspace" option is enabled.

Reproducible: Always

Steps to Reproduce:
<project name="samples" default="help" basedir=".">
	<target name="help">
		<input message="Enter one of the options:" addproperty="foo.bar2" validargs="y,n">
			<handler type="default" />
		</input>
	</target>
</project>
Comment 1 Eclipse Genie CLA 2019-09-09 18:24:13 EDT
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.