[GRADLE-579] Create a gradle Shell Created: 31/Jul/09 Updated: 10/Feb/17 Resolved: 10/Feb/17
A feature which could be called "gradleShell" should be available for a better support of reoccurring tasks.
I want gradle to enter a shell mode when it is called with gradle -S. After gradle has entered shell mode, it accepts all parameters that you could provide when calling gradle regularly (gradle <params>).
The input sequence:
Would execute the compile-Task for two times. However, the gradle process is running through the complete sequence which saves some time (JVM is only started once). I attached a patch for this functionality.
Unfortunately, the implementation is still a bit buggy as it only outputs logging messages of the first task invocation. Example:
Total time: 2.969 secs
I debugged this till up to the java.io.writer but couldn't find out, why the expected output is not written to the console...
|Comment by Matthias Pfau [ 31/Jul/09 ]|
The last example is formatted wrong, it should have been:
|Comment by Hans Dockter [ 02/Aug/09 ]|
This would be a very cool feature. Steve Appling and his team are working on a standallone UI client. This should merge into trunk pretty soon. The shell and the UI client might be able to share some common functionality. I will have a look at your patch ASAP.
|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:
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.