Issue with Java Destination in Airbyte Generator

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

In a previous version of Airbyte, there was an issue with the Java Destination generator where Gradle fails to locate the destination project, hindering the Docker image building process. However, the new Java source connector project works smoothly with Gradle.


Question

In a previous version of Airbyte, the generator included an option to select a Java Destination, but I’m encountering an issue where Gradle fails to locate the destination project, preventing me from building the Docker image. However, new Java source connector project operates smoothly with Gradle.


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["java-destination", "gradle", "docker-image", "connector", "airbyte"]
2

The issue arose because the newly created destination connector project lacked a metadata.yaml file. In the settings.gradle, during the process of including the connector projects, it checks for the presence of both metadata.yaml and gradle.build files in each connector project. If these two files are missing, then the connector is not included in Gradle.

3

and generator does not generate metadata.yaml for destination connector.