[GRADLE-3039] Init-script specified at command (-I/--init-script) should be executed last, so command line trumps default. Created: 04/Mar/14 Updated: 10/Feb/17 Resolved: 10/Feb/17
The facility exposed for init-script is good, however one normally expects command line operations to always trump default operations. This would easily be accomplished by changing the order of operations to be command line last.
As currently written, init-script specified on command line is least preferable, which is odd.
|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.