[GRADLE-2754] Reading project.properties triggers configuration of any DeferredConfigurable extensions Created: 18/Apr/13 Updated: 10/Feb/17 Resolved: 10/Feb/17
We are using the new incubating [PublishingExtension](http://www.gradle.org/docs/1.5/dsl/or...) and registering an [IvyPublication](http://www.gradle.org/docs/1.5/dsl/or...) in its publication container. Since we need to manually populate the `IvyPublication` with all artifacts from all configurations, we are relying on the deferred configuration support for this extension, and thus expect that the extension will be configured at the last possible moment so that all artifacts are already available.
Unfortunately it turns out that reading the project properties using project.properties is triggering the configuration of the publishing extension and thus reading all configuration artifacts too early.
P.S. We are using Gradle 1.5
|Comment by Gradle Forums [ 18/Apr/13 ]|
Dev list discussion can be found here: http://gradle.1045684.n5.nabble.com/C...
|Comment by Henry Tung [ 18/Dec/15 ]|
Can confirm that this issue remains, and still affects Gradle as far as version 2.9.
For reference, the relevant stacktrace from the following build.gradle block shows where the errant execution takes place:
yields the trace:
|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.