Yes, that would be a task for the Tooling Script. I mentioned it a few
times here and there, that the tooling script is one of the
weakest/strongest (depends on the point of view). It's kind of ugly,
hard coded, not that easy to change. On the other hand it serializes the
data into simple core
Laszlo -
I've tried to find out how could a plugin inspect details of a Task
configured for a gradle project -- but so far I haven't found a way how
to dig out e.g. properties (primitive ones could be sufficient, maybe) ?
Is there a way or model in current Gradle support that I've missed ? The
