Since you are bypassing the automated Resolution Strategy of the Plugin Portal, you often have to use the "old" way of applying plugins via the buildscript classpath:
buildscript { repositories { flatDir { dirs 'local-plugins' } } dependencies { // Use the filename and version of the JAR you downloaded classpath name: 'plugin-filename-1.0.0' } } // Apply it by ID apply plugin: 'com.example.my-manual-plugin' Use code with caution. Alternative: Using a Local Maven Repository download gradle plugin manually
Once you have the files, you need to put them in a structure that Gradle understands. The easiest way to do this is to create a "flat directory" repository within your project. Create a folder in your project root named local-plugins . Place your downloaded .jar files inside this folder. Step 3: Configure Gradle to Use the Manual Files Since you are bypassing the automated Resolution Strategy
If the plugin you are downloading has many dependencies, a flatDir might fail because it doesn't handle POM files (metadata) well. In this case, it is better to: Create a folder in your project root named local-plugins