Issue using the API Gateway Policy Plugin

Products

• CA API Gateway
• API SECURITY
• CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7)
• CA API Gateway Enterprise Service Manager (Layer 7)
• STARTER PACK-7
• CA Microgateway

Issue/Introduction

The user is trying to follow the example from the documentation: https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/gateway-policy-plugin/1-0/getting-started.html

stepped through the various config items on my Windows machine:

                Docker desktop (v19.03.13) with WSL2 engine

Gateway 10 policy manager

                Java (openjdk 1.8.0_265)

                Gradle (6.7)

                Git (2.26.2.windows.1)

They can deploy the demo gateway on docker, and connect to it with the policy manager.  Gradle seems to work too – it does not report any startup errors.  Cloning git repositories works fine too.

However when they try to do a clean export (gradle export clean), I get an error:  Failed to apply plugin ‘com.ca.apim.gateway.gateway-export-plugin’, could not create instance of type com.ca.apim.gateway.cagatewayexport.config.GatewayExportPluginConfig.

Looking through the trace, it looks like gradle has managed to cache gateway-export-plugin-1.0.2.jar.  I believe that is the latest available version. 

I have checked the local .gradle cache and it does have a gateway-export-plugin-1.0.2.jar file.  

The customer's  original attempt was based around Intellij Community – that gives exactly the same error.

What have I done wrong, or what do I still need to add? 

Environment

Release : 10.0

Component : API GATEWAY

Resolution

Advised the customer to follow the instructions below which resolved the above problem.

run this command and verify what you get.
>> gradle clean export --stacktrace --debug

If your export fails showing any build failure exception as shown below, it would mostly be gradle version incompatibility:

Check your gradle version using the gradle --version command and ensure the version is 4.10.
You can also use a gradle wrapper to fix this issue:

Add the following section in your build.gradle file:
wrapper {
gradleVersion = '4.10.2'
}

Run the following command:
>> gradle wrapper

Run your gradle tasks using the gradle wrapper:
./gradlew clean export