apiproject.log hangs during Gradle build
When the z/OS® Connect Designer container is started, the API Project is built and then deployed to z/OS Connect Designer.
In some instances, container networking issues that are often caused by Proxies, can cause this build to get stuck while it attempts to resolve dependencies. As a result, the API is not made available for testing.
About this task
Within the API Project, the following change can be made to give preference to local dependencies packaged within the z/OS Connect Designer image for API Project build.
- Stop the z/OS Connect Designer. For more information, see Starting and stopping z/OS Connect Designer.
- Open /myApiProject/build.gradle and move
mavenCentral()to the end of the
repositoriessection. Save and exit.Note: /myApiProject/ is the project workspace directory.
- Open /myApiProject/settings.gradle and move the
gradlePluginPortal()to the end of the
repositoriessection. Save and exit.
- Start the z/OS Connect Designer container
again and review apiproject.log to see whether the build is successful. For
more information, see Starting and stopping z/OS Connect Designer. Note: The Gradle Daemon can take 60 - 90 seconds to start.