Open aSemy opened 2 years ago
I think we should be careful with this, and ensure that it doesn’t get harder than the current instructions. My experience with this is that a custom plug-in sometimes fail on Android or MPP, for which KSP has special instructions.
Yeah, the plugin instructions would be easier if the KopyKat plugin can be published to Maven Central or the Gradle Plugin Portal. JitPack manually overrides the project's group, which in turn breaks the Gradle plugin marker. If published on Maven Central, the resolutionStrategy {}
workaround isn't needed.
The plugin in this PR shouldn't cause problems with Kotlin Multiplatform, but users might have to manually enable KSP per source set. There's ways to test for this though, either manually with example projects, or with Gradle TestKit. I can include them in this PR, if you'd like? But I think that would make it too large.
Can you find the special instructions for Android? I could only find them for Kotlin Multiplatform.
I'm working on publishing to Maven Central (#41), which should make things easier
Here's an initial attempt. It's still a little rough, but it's ready for a first look.
fixes #29
It requires some setup:
import the plugin
Notes: