I would recommend using a maven-managed project. All required artifacts to create such a project are on the public 52north maven repository (including the XML bindings library you mentioned). The following pom.xml should serve well as a project skeleton. It already has the aforementioned maven repository included.
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>my.test.wps-project</groupId>
<artifactId>wps</artifactId>
<version>0.0.1-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.n52.wps</groupId>
<artifactId>52n-wps-io</artifactId>
<version>3.1.0</version>
</dependency>
<dependency>
<groupId>org.n52.wps</groupId>
<artifactId>52n-wps-algorithm</artifactId>
<version>3.1.0</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.11</version>
<scope>test</scope>
</dependency>
</dependencies>
<repositories>
<repository>
<id>n52-releases</id>
<name>n52-releases</name>
<url>http://52north.org/maven/repo/releases/</url>
</repository>
</repositories>
</project>
In general, artifacts of a maven-managed open source project should be accessible on a dedicated or central repository. Otherwise the projects build setup would not be satisfied. So, a general advice would be to first do some investigation on the project structure.