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?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| How to determine set of inputs to build configuration (not to tasks themselves) | 0 | 8 | March 11, 2025 | |
| Properly define up-to-date values for Task which uses dependencies as input | 1 | 710 | April 29, 2015 | |
| How to get inputs path in plugins for validation user message | 0 | 427 | August 6, 2018 | |
| Task inputs and outputs from extension? | 3 | 2948 | February 7, 2013 | |
| Can I get a list of input files that has changed since the previous build? | 1 | 2143 | November 17, 2014 |