Quantcast
Channel: Gradle Forums - Latest posts
Viewing all articles
Browse latest Browse all 19854

Chicken/egg issue with dependency configuration setup and "task configuration avoidance"

$
0
0

I understand what you are saying but that significantly increases complexity. Instead of the tasks “knowing” whether they need a version or not, or having the version be something otherwise “asked for”, I’d have to implement and maintain a dedicated subsystem just to handle this case … and that system would have to “know” about each and every task’s version needs… That is way too much effort for the value it brings and, in my view, should not really have to be done. If everything (or these things) were lazily initialized (when needed = on access, not before) we wouldn’t need this complexity.


Viewing all articles
Browse latest Browse all 19854

Trending Articles