This message was deleted.
# plugin-developments
Slackbot
02/08/2022, 7:58 PMThis message was deleted.
c
CristianGM
02/08/2022, 8:15 PMYou cannot set the version of the plugin in your test build.gradle, you need to add it to the classpath
CristianGM
02/08/2022, 8:16 PMWithPluginClasspath is the usual way
CristianGM
02/08/2022, 8:18 PMIf you want to use other versions...
You can create another configuration and do ..
// Inspired by: https://github.com/square/sqldelight/blob/83145b28cbdd949e98e87819299638074bd21147/sqldelight-gradle-plugin/build.gradle#L18
// Append any extra dependencies to the test fixtures via a custom configuration classpath. This
// allows us to apply additional plugins in a fixture while still leveraging dependency resolution
// and de-duplication semantics.
tasks.named("pluginUnderTestMetadata", PluginUnderTestMetadata::class.java) {
pluginClasspath.from(fixtureClasspath)
}
v
Vampire
02/08/2022, 9:23 PMAnd if you want to use second approach, better use a dedicated directory instead of
mavenLocal()👍 3
m
Maerov Timofey
02/09/2022, 8:37 AMI want use WithPluginClasspath way! But it fail, because gradle do not resolve all dependency for kotlin plugin, and i have ClassNotFoundException
Maerov Timofey
02/09/2022, 8:48 AMI was expecting the WithPluginClasspath way to resolve the same kotlin dependencies as publicToLocalMaven. But that's not true.
Same project with publicToLocalMaven way build successfully, but with WithPluginClasspath way faild with ClassNotFoundException
Maerov Timofey
02/09/2022, 9:00 AMif these methods lead to different sets of dependencies, then should i prefer publicToLocalMaven because it's more reliable?
Maerov Timofey
02/09/2022, 9:07 AMCristian, i read you note, and try to analyze you repository, but it is so hard for me. As I understand it, you were talking about extra dependencies, but I have a problem with core gradle dependencies(kotlin-gradle-plugin-api missing)