[GRADLE-2462] BuildLauncher.setStandardInput does not forward input until EOF has been reached. Created: 04/Sep/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.1
Fix Version/s: None

Type: Bug
Reporter: Attila Kelemen Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

I have attempted to use BuildLauncher.setStandardInput to provide the ability for the user in NetBeans to provide input for the script. However, I have noticed, that the input provided by the above mentioned InputStream is not available for the script until the InputStream returns EOF. EOF is never normally sent, since that would prevent the user to provide additional input.

To reproduce the problem call "System.in.read()" in a task of a build script, and provide an InputStream for BuildLauncher.setStandardInput which never returns EOF. The read method will block and wait forever. The expected behaviour is that the read method returns after providing even a single byte.

 Comments   
Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:22:34 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.