Closed Jolanrensen closed 4 months ago
After investigation:
df dokka 1.8.20 korro 0.1.6 - dokka 1.8.20 no doc preprocessor works
df dokka 1.8.20 korro 0.1.5 - dokka 1.8.10 no doc preprocessor works
df dokka 1.9.10 korro 0.1.6 - dokka 1.8.20 no doc preprocessor works
So I suspect korro is safe :) docProcessor is the culprit
Continuing:
df dokka 1.8.20 no korro doc preprocessor 0.3.2- dokka 1.8.10 works
df dokka 1.9.10 no korro doc preprocessor 0.3.2- dokka 1.8.10 works?
df dokka 1.8.20 korro 0.1.6 - dokka 1.8.20 doc preprocessor 0.3.2- dokka 1.8.10 works
df dokka 1.9.10 korro 0.1.6 - dokka 1.8.20 doc preprocessor 0.3.2- dokka 1.8.10 works?! huh?
I don't get it. It broke last time. Some gradle cache maybe?
Edit: I did these tests with clean assemble
. I'll now retry with clean build
as it looks like other stuff might break with that.
using clean build
df dokka 1.8.10 korro 0.1.5 - dokka 1.8.10 doc processor 0.3.2 - dokka 1.8.10 works
df dokka 1.8.10 korro 0.1.6 - dokka 1.8.20 doc processor 0.3.2 - dokka 1.8.10 breaks linter :(
df dokka 1.8.20 korro 0.1.5 - dokka 1.8.10 doc processor 0.3.2 - dokka 1.8.10 works
df dokka 1.9.10 korro 0.1.5 - dokka 1.8.10 doc processor 0.3.2 - dokka 1.8.10 works
df dokka 1.9.10 korro 0.1.6 - dokka 1.8.20 doc processor 0.3.2 - dokka 1.8.10 breaks linter
All dokka dependencies are stuck on v1.8.10 until korro and docProcessor update their dokka versions to 1.9.10 as well.