From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I am not sure, can be hard to say Gradle where the project is, because each machine can create the test in a different place and so on

but I guess that if this is not easy to get with test kit, I should create a feature request, I think it is a common use case

There was feature request for testkit to support composite builds iirc.
For now you can publish all into a repo local to a project and add it to the project under test

yeah, that is what I was doing but I was trying to avoid it

I will keep doing that until there is a new way to get it working without publishing

If metadata for plugin under test is simple classpath maybe generating it would work? Never tried myself

I have no idea about that tbh, so I don't know how to start to try that hahah

hm, <https://github.com/gradle/gradle/blob/master/subprojects/plugin-development/src/main/java/org/gradle/plugin/devel/tasks/PluginUnderTestMetadata.java|https://github.com/gradle/gradle/blob/master/subprojects/plugin-development/src/main/java/org/gradle/plugin/devel/tasks/PluginUnderTestMetadata.java> tells that your plugin runtime classpath should already be on the testkit classpath

Mb I could have missed a major point. I reread original post and if I understand correctly it's not your plugin that use core but project that use the plugin? Afaik plugin under test metadata defines classpath for the build script

i tried to find that classpath to extract all dependencies, but that classpath doesn't exist, and I tried to find all classpath dependencies, but that dependency wasn't there