GradlePlugin | Gradle plugin for obfuscating strings | Plugin library

I don't know if it is critical for your problem but modifying this

After a bit of digging and exploring some open source projects, I found the solution for the above issue. Initially, I was using the distributionUrl=https\://services.gradle.org/distributions/gradle-7.0.2-bin.zip as my Gradle version in gradle-wrapper.properties but to fix the issue I updated the Gradle version to 7.3.2

So changing the distribution URL to distributionUrl=https\://services.gradle.org/distributions/gradle-7.3.2-all.zip fixed the issue for me

This is what I've found so far, not sure if there's a more fluent way to do it:

The solution is to add the dependency in the dependencies block of the build.gradle of the custom gradle plugin project.

https://docs.gradle.org/current/samples/sample_convention_plugins.html

The task ValidatePlugins does not check plugin metadata but perfoms static code analysis on the plugin classes:

Validates plugins by checking property annotations on work items like tasks and artifact transforms. This task should be used in Gradle plugin projects for doing static analysis on the plugin classes.

The output you see during the build matches what is described in the documentation of java-gradle-plugin. It reads

[...] performs validation of plugin metadata during jar task execution.

And further

Any failed validations will result in a warning message.

You should use Gradle 6.8, it includes Kotlin 1.4.20.

When you have the plugin jar on the classpath, you can't have a version number in the plugin application. I guess this is because you can't have multiple jars with different versions on the classpath in the first place, so specifying a version here doesn't make any sense (except perhaps to validate that you are using the correct one). This won't fix the problem, but it is a start.

To be honest, I don't know why your approach still won't work. The buildscript block is supposed to set up dependencies for that particular script, and that should make the plugin visible to it. It doesn't for some reason.

Perhaps this is a bug or perhaps this is just an undocumented limitation on the use of the plugin {} block. Maybe you could ask over at the Gradle forums or create an issue for it. However, there are workarounds that don't involve publishing to a (local) Maven repository, which I agree can be a bit annoying.

If you use "apply from" instead of "plugins {}", it works. For some reason, the former can see the buildscript classpath whereas the latter can't:

I could achieve this with the following gradle configurations

• Copy all the dependent jars to a directory

It turns out there were a couple of issues in my code

1. I was missing .withPluginClasspath() on the GradleRunner
2. The TestKit doesn't need group prefix, plugins { id 'example' }