SOAP-DTC Development

We are always looking for contributions, so feel-free to send patches to our issues tracker. Please do us a favour by sending the patches in unified diff format against the latest version in the SVN trunk instead of whole source code files. If you add features, please don’t forget to document them.

The project is run as a meritocracy, so after a few good contributions, you can get promoted to a developer position if you are inclined to step-up.

The source code is managed through Subversion, so please refer to the Google Code page of the project. You can check out the source code anonymously, but commiting is restricted to developers.

We follow the classical way to manage a project with Subversion:

• the development version is in the trunk
• the stable branches (ex: 1.2.x) are located under branches
• snapshot of releases (ex: 1.2.1) are located under tags.

We suggest that you read the Subversion book if you are not familiar with Subversion.

The build is handled by Maven2. If you prefer working with Ant, please let-us know and write a good Ant build file that downloads the dependencies and achieves the same goals. We will be pleased to include it if proven to be good.

We have flattened the Maven modules layout, so that you can work on the source code with the IDE of your choice, be it Eclipse, Netbeans, IntelliJ IDEA or just plain-old-good text editors.

Once you have a running Maven installation, go to the soap-dtc module (which is the parent one). From there you can build the source code (mvn compile), test it (mvn test) or install it in your local maven repository (mvn install).

You can generate project support files for Eclipse and IntelliJ IDEA. To do that, you will need to get the source code and have Maven working as explained above.

Move to the soap-dtc/ folder, then simply run the idea:idea goal in Maven.

cd soap-dtc
mvn idea:idea

The procedure is similar to the one for IDEA.

cd soap-dtc
mvn eclipse:eclipse

This has generated project files for the soap-dtc-core and soap-dtc-server projects (soap-dtc does not contain source code, hence Maven does not create a project for this one).

The next step is to configure the M2_REPO variable in Eclipse, so that it can locates the libraries used by the projects. In the Eclipse preferences, go to Java > Build Path > Classpath Variables, then create the M2_REPO variable to point to your Maven local repository (ex: /home/julien/.m2/repository/).

You can now import the projects in Eclipse: File > Import > Existing project into Workspace.

Have fun!