# What is best way of logging all the inputs to a task?

**URL:** <https://discuss.gradle.org/t/what-is-best-way-of-logging-all-the-inputs-to-a-task/14431>\
**Category:** Help/Discuss\
**Created:** [February 11, 2016, 6:50pm UTC](https://discuss.gradle.org/t/what-is-best-way-of-logging-all-the-inputs-to-a-task/14431 "2016-02-11T18:50:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sc1478](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/sc1478/32/4341_2.png) [@sc1478](https://discuss.gradle.org/u/sc1478)\
**Post date:** [February 11, 2016, 6:50pm UTC](https://discuss.gradle.org/t/what-is-best-way-of-logging-all-the-inputs-to-a-task/14431/1 "2016-02-11T18:50:25Z")

</div>

With “plugin composition” there are many possible places where inputs to a build may come from. One or more layers of convention, extension properties, etc. What API on a task callable from a doFirst() would show the collection(s) of all inputs that are in force at the runtime of the build?