ClassCastException with Gradle 7.5-milestone-1

[juergenzimmermann]

ClassCastException with Gradle 7.5-milestone-1

[pavelicii]

Issue persists with Gradle 7.5.

[vlsi]

The culprit is

allure-gradle/allure-base-plugin/src/main/kotlin/io/qameta/allure/gradle/base/tasks/AllureExecTask.kt

Line 71 in 1d1b058

mustRunAfter(resultsDirs)

[juergenzimmermann]

As expected: issue persists with Gradle 7.5-rc-2

[juergenzimmermann]

The issue still exists with io.qameta.allure 2.10.0

[juergenzimmermann]

Gradle 7.5.1: Hopefully not "The same procedure as every year" https://www.youtube.com/watch?v=Nysm_ErwdFE ;-)

[AM1988]

Hey. Any plans to fix this? Does anyone have a workaround?

[CristianGM]

I can fix it quite easily but it implies requiring Gradle 6.8.3+

making it compatible, if possible, would require a lot of work, and 6.8.3 is from Feb 2021, not precisely new.

What do you think?

meh, not yet...

[CristianGM]

I jumped to the pool but it didn't have water...

Moving the project to Gradle 7.5 and fixing a ton of things is not enough.
Making the tests to use Gradle 7.5.1 makes them to fail with the same error. The issue seems to me when it resolves dependencies to run AllureReport.

[vlsi]

The relevant line in 7.5.1 is https://github.com/gradle/gradle/blob/v7.5.1/subprojects/core/src/main/java/org/gradle/execution/plan/LocalTaskNode.java#L134, so it is probably connected with mustRunAfter.

[vlsi]

I've filed gradle/gradle#21962 for Gradle team to analyze, however, I do not see a relevant workaround.
I am afraid what we can do at allure-gradle side right now is to skip mustRunAfter(resultsDirs) by default when running with Gradle 7.5+.

It turns out there's a workaround: mustRunAfter(resultsDirs.map { it.elements }).

[juergenzimmermann]

@vlsi @baev The upgrade to Gradle 7.6-milestone-1 works fine. Thank you for your efforts!