[GRADLE-1855] GUI property-setting ability is inadequate Created: 20/Oct/11 Updated: 16/Jan/17 Resolved: 16/Jan/17
The only way to change Gradle build properties or Java system properties with the Gradle GUI is to use the Command Line tab, thereby eliminating all benefit of using the GUI.
I understand that the Command Line workaround may be acceptable to support some special situations, but build properties are an essential component of doing Gradle builds, and the GUI should not be changed to an impediment to productive work just because a task needs to be re-run with a different setting (via Gradle build property). System properties settings are less essential, but could probably be accommodated easily enough with the same GUI enhancement.
My current work-around is to have the builder edit a build properties file in an independent session (i.e., unrelated to the Gradle GUI process). Should not need to use work-arounds just to make use of Gradles' most basic features.
|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 Blaine Simpson [ 15/Nov/16 ]|
Still makes the Gradle gui unusable for many realistic use cases.
|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.