[
https://issues.apache.org/jira/browse/GEODE-6019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-6019:
----------------------------------
Labels: pull-request-available (was: )
> Gradle constants should be declared in gradle.properties when possible
> ----------------------------------------------------------------------
>
> Key: GEODE-6019
> URL: https://issues.apache.org/jira/browse/GEODE-6019
> Project: Geode
> Issue Type: Improvement
> Reporter: Patrick Rhomberg
> Priority: Major
> Labels: pull-request-available
>
> Build constants, such as the project {{group = org.apache.geode}}, should be
> declared in the {{gradle.properties}} whenever possible, rather than in the
> {{build.gradle}}.
> * As a constant, it needs not clutter our already-rather-involved build graph.
> * In many places, because project properties are read-only after
> initialization, we resort to {{ext}} to write property values, which are not
> robustly cached for performance (though this impact is likely trivial)
> * In some instances, such as third-party developers or particularly testing
> scenarios, we may wish to overwrite these constants on the command-line,
> which cannot be done when they are declared in {{build.gradle}}
> configurations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
