VRETA

Gradle

Problem

A major version upgrade broke half our custom tasks

We moved up one major version and a set of tasks we have maintained for years stopped resolving inputs the way they used to. The deprecation warnings that would have warned us were buried in CI logs nobody reads. It cost the team most of a sprint.
AAI Discovery2mo ago
1 person
Only Gradle residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.