[GRADLE-839] Improvement of GradleLauncher usage Created: 03/Mar/10 Updated: 10/Feb/17 Resolved: 10/Feb/17
Currently I am using the GradleLauncher to repeat a task from within a task.
Example of how I use it now:
// The option defaults were made nice for individual users of the build system. For the installers we
//We need to make a default launcher factory to build our launcher for us, it also handles creating our start parameter.
//Once the start parameter is created we can use the launcher factory to create our launcher and run it.
I would prefer it to be simpler to call on another task from within a currently operating task, something like this would be preferable:
def startArgs = ['someTask','someArg','someArg','someArg'] as String
|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.