Replies: 1 comment
-
This is an issue with variant resolution. There are existing bugs on this #89. However this problem should be resolved with recent versions of the Kotlin gradle plugin and Gradle. They should be providing the dependency resolution attribute for the correct platform. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I understand that this issue may not be directly related to this library, but it seems to be more of a Gradle-related problem. However, I still want to ask here to see if anyone has experienced something similar or has any suggestions. At the very least, I hope to gain some direction because I'm quite perplexed by the issue.
I am attempting to use this library within my Gradle plugin. The Gradle plugin is located within the same project and is meant to be utilized by other modules.
The build process is successful when the library is not used by other modules. However, as soon as I attempt to use the plugin in one of my modules by adding
id("com.zeroarst.xmlutil")
to thebuild.gradle.kts
file, I encounter a myriad of errors.I have thoroughly reviewed the error messages but have not been able to discern their meaning or root cause.
I have created a repository to reproduce the issue, and it can be found at the following link
https://github.com/zeroarst/replicate-xmlutil-as-a-plugin-issue/tree/master
So the repository has two modules, one is app, the other is xmlutil-plugin. App is just a normal app, and xmlutil-plugin is built as a gradle plugin. When sync the project with Gradle, it just throws a lot of errors. I attach the log below. This is due to app uses the plugin
xmlutil-plugin
in itsbuild.gradle.kts
, with this lineid("com.zeroarst.xmlutil")
.The repository consists of two modules:
app
andxmlutil-plugin
. Theapp
module is a typical application, whilexmlutil-plugin
is built as a Gradle plugin. Upon synchronizing the project with Gradle, it generates numerous error messages. It appears that the errors are related to the serialization aspect of the plugin, as when I use only the 'core' aspect, no errors occur.If anyone has encountered a similar issue or has any suggestions, I would greatly appreciate your assistance in resolving this problem.
Errors:
Beta Was this translation helpful? Give feedback.
All reactions