Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

Hi,
I’m following the steps to <https://docs.airbyte.com/contributing-to-airbyte/developing-locally/|build Airbyte for local development> to be able to test a change to a connector I’ve been working on.

However, when running `SUB_BUILD=PLATFORM ./gradlew build` I get

```FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':spotlessJava'.
&gt; java.lang.reflect.InvocationTargetException```
This is happening *even on master* for me. Any help is appreciated

```&gt; Task :spotlessJava FAILED
Step 'removeUnusedImports' found problem in 'airbyte-analytics/src/main/java/io/airbyte/analytics/SegmentTrackingClient.java':
null
java.lang.reflect.InvocationTargetException....```

Hey <@U02UJ3MMA3F> could you try to pull master again and check if the error persists? For  connector development questions do you mind posting on our <https://discuss.airbyte.io/c/connector-development/16|forum>?

Hey <@U02UC3T12PJ>.. I’ve already pulled from master and <https://discuss.airbyte.io/t/failure-to-build-airbyte-from-master/1410|posted on the forum>.
The reply from <@U02TQLBLDU4> there is that I don’t need to build the platform entirely. But I want to test if my connector is working through the UI, if I don’t build the entire solution I won’t have the containers tagged as _dev_ and consequently I can’t spin up the environment in _dev_ mode. I’m trying to follow the below and failing on the first command:

```SUB_BUILD=PLATFORM ./gradlew clean build
VERSION=dev docker-compose up -V```

You don’t need to build the platform to build your connector. Only run `./gradlew airbyte-integrations…:your-connector:build` which will build your your-connector:dev

Even if you build the entire project your connector won’t show up in the list because was not added in the seed file

Let me try to build the connector. I might need some follow up help.
Btw, I’m making a change to an existing connector adding incremental load to it. So the connector is there just not the “incremental” capability

image.png

so, after running the grsdlew command you only need to change the version to dev

ok I’ve just finished building my connector by running `./gradlew :airbyte-integrations:connectors:source-azure-table:build`

The application I have up and running is the one that pulls images from dockerhub (`docker-compose up`) When I build it should the build create a new image/container tagged as dev?

wondering because I can’t see it by running `docker image ls`

if the command run succesfully it should created a airbyte/source-azure-table:dev connector

./gradlew :airbyte-integrations:connectors:source-azure-table:airbyteDocker

ok I can see a container built

```REPOSITORY                       TAG             IMAGE ID       CREATED              SIZE
airbyte/source-azure-table       dev             9a1f3ae8f0a0   37 seconds ago       115MB```
Now I’ll `docker-compose up` and see if I can update the connector to point to my container