Use TaskCollection.named overload taking Spec

[lukellmann]

Use the new TaskCollection.named method taking a Spec for depending on tasks that might not exist.

See https://docs.gradle.org/8.6/release-notes.html#lazy-name-based-filtering-of-tasks

[lukellmann]

btw, what the reason for this commit? asking to make sure this won't conflict with that change.

[DRSchlaubi]

For some reason named thrw an exception when the task doesn't exist. Did you test this on kord

[lukellmann]

Did you test this on kord

not yet, how would i best do this?

[DRSchlaubi]

Push to Maven local

[lukellmann]

For some reason named thrw an exception when the task doesn't exist.

makes sense, it's documented to do so: https://docs.gradle.org/current/javadoc/org/gradle/api/NamedDomainObjectCollection.html#named-java.lang.String-

[DRSchlaubi]

ig this doesn't matter when using the predicate

[lukellmann]

yes, it's just gonna be an empty collection and dependsOn seems to just accept that

[lukellmann]

Did you test this on kord

i did, it works after fixing this npe and running kord's build with gradle 8.6

[lukellmann]

with kordlib/kord#920 kord will use gradle 8.6