[GRADLE-1365] Allow override of plugin convention property with project property Created: 03/Feb/11 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | 0.9.2 |
Fix Version/s: | None |
Type: | Improvement | ||
Reporter: | Mark Ingram | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 5 |
Issue Links: |
|
Description |
I am trying to understand how to set a plugin convention property from a project property. Here is the customPluginWithConvention example from the gradle distribution (gradle-0.9.2\samples\userguide\organizeBuildLogic\customPluginWithConvention\build.gradle) apply plugin: GreetingPlugin greeting = 'Hi from Gradle' class GreetingPlugin implements Plugin<Project> { } class GreetingPluginConvention { Running this script with no project property: >gradle hello BUILD SUCCESSFUL And now trying to set a custom message via setting a project property: >gradle -Pgreeting=goodbye hello Instead of the expected "goodbye" the default greeting of the convention is shown. Is it possible to override the message? <<Peter Niederwieser>> Not yet, but we should try to make it possible. Please create an issue at http://jira.codehaus.org/browse/GRADLE. |
Comments |
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. |