[GRADLE-1168] GUI should allow some way to provide character input to interactive child processes Created: 08/Oct/10  Updated: 17/Jan/17  Resolved: 17/Jan/17

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

Type: Improvement
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Duplicate Votes: 11

Comment by Matias Bjarland [ 25/Jun/11 ]

This issue seems related to GRADLE-1147. Assuming we by "character input to interactive child processes" mean the ability to get user input from the console, we seem to have two facts affecting the ability to do this in the current 1.0m3 release:

  • As per GRADLE-1147, the only way to not have the gradle progress logging pollute your console prompt when prompting for user input is to run java >= 6 (the System.console() call and the Console class are java 6 artifacts) and use the Console class returned by the System.console() call.
  • The System.console() call returns null if running using "gradle --daemon".

So if you run java 6 and do not run using --daemon, there is a good way for doing this. You can also run your gradle build using "gradle -q", but as that is not the default I don't find this solution quite acceptable either. The issue is exasperated by the fact that "--daemon" is (as far as I understand) going to be the default in future releases of gradle.

Comment by Adam Murdoch [ 25/Jun/11 ]

We won't switch on the daemon as the default until there is some way to get input into the daemon process. The plan is that you will be able to read input via System.in regardless of which UI is used to launch the build.

In the case of launching from the command-line, input from the command-line terminal will be made available in the daemon process.

For GUI interfaces, we will provide some way for tooling api clients to provide input to be made available in the daemon process. It is then up to each GUI to make use of this.

Comment by Matias Bjarland [ 12/Mar/12 ]

Any updates for this issue? Can't seem to find any on the forums or in JIRA for the current (m8) release and this is still an issue for us. Also with the current release being daemon friendly to the point where all our devs are using daemon as default, getting character input from the daemon process has become a priority.

Comment by Matt Hauck [ 06/Sep/13 ]

Any hope for this being resolved?

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 Chris Jones [ 23/Nov/16 ]

This is still an active request.

Comment by Matias Bjarland [ 30/Nov/16 ]

+1, this is still and active request.

Comment by Benjamin Muschko [ 16/Jan/17 ]

The Gradle GUI has been deprecated and is scheduled to be removed with Gradle 4.0. We are not going to work on this issue anymore.

Comment by Matias Bjarland [ 17/Jan/17 ]

This issue is not about the "gradle gui" but rather about the console "user interface", i.e. about giving the build user the ability to interact with the console build in a clean way.

Comment by Benjamin Muschko [ 17/Jan/17 ]

@Matias Thanks for clarifying. The title was fairly misleading. I am marking this issue as duplicate of https://issues.gradle.org/browse/GRADLE-1147.

Generated at Wed Jun 30 11:48:42 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.