# Assemble the Connector

After creating a connector module (e.g., AmazonQ), update the following files.

Parent pom.xml (repo root)

**Add the module**

```
<module>amazonq</module>
```

**csp-api/pom.xml**

Add dependency

```
<dependency>
 <groupId>com.ovaledge</groupId>
 <artifactId>amazonq</artifactId>
</dependency>
```

**assembly/pom.xml**

Add the same dependency to include the connector in the assembly JAR.

**SPI Registration**

Ensure the connector is registered in:

```
META-INF/services/com.ovaledge.csp.v3.core.apps.service.AppsConnector
```

**Release properties**

* Every connector JAR must include a \`release-{artifactId}.properties\` file in its resources (e.g., \`release-amazonq.properties\`) with at least: \`{artifactId}.release.version\`, \`{artifactId}.git.commit.full\`, \`{artifactId}.git.branch\`, \`{artifactId}.git.buildtime\`.&#x20;
* Connectors created from the archetype get a template and a test (\`CspSdkConnectorReleaseTest\`) that uses connector-release-support to generate this file at build time. Existing SDK connectors (e.g., monetdb, amazonq) use the same test.
* Partners building connector JARs outside this repo must ensure their build produces an equivalent \`release-{artifactId}.properties\` so the CSP runtime can identify and audit connector versions.
* Run the command below to verify that the new connector is discovered (e.g., GET /v1/info shows it) and included in the assembly JAR.

  ```
  mvn clean install -pl amazonq -am
  mvn clean install -pl csp-api -am
  # or
  ./build-csp-sdk.sh
  ```

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.\ <br>