Binary and data dependencies required to enable CTS APIs are littering existing repositories with little increase in value. Instead, this can turn into a central binary repository for all third-party jars not cleanly hosted elsewhere.
First make sure you understand what a maven artifact repository. Then jump into your pom.xml file and add the releases and snapshots repositories. For comfort, the repositories tag that encompasses each repository has been added. At the time of this release, both branches are identical, but may diverge over time.
<repositories>
<repository>
<id>EPA CTS Maven Release Repository</id>
<url>https://github.com/pavgup/cts-mvn-repo/raw/master/releases</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>EPA CTS Maven Snapshot Repository</id>
<url>https://github.com/pavgup/cts-mvn-repo/raw/master/snapshots</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
