ralf
08/23/2019, 11:21 PMafterEvaluate
internally, but at this point when it calls the method it’s too late. With evaluateDependsOn
you change the order. C gets evaluated earlier now and the Kotlin plugin for C calls afterEvaluate
during the right phase. I think it’s still worth filing a bug, but I didn’t have a repro case.