Setting up a development environment

If you are planning to modify or explore the OTP source code at all, you will probably want to work on OTP within an Integrated Development Environment which will provide automated compiling, debugging, and syntax-aware indexing and refactoring. The IDEs most commonly used by OTP developers are Eclipse, IntelliJ IDEA, and Netbeans.

Working with the master branch

Setting up a development environment for OTP used to be a rather irritating process, but things have been greatly simplified recently. The master branch of OTP no longer requires you to navigate the complexities of a multi-module Maven build, deployment to a servlet container, Spring-based configuration, or Lombok IDE plugins. This makes it much easier to dive in to the OTP code base than in the past.

Specific information is available for each of the above-mentioned IDEs:

• Setting-up-a-development-environment-in-IntelliJ-IDEA
• Setting-up-a-development-environment-in-Eclipse
• Setting-up-a-development-environment-in-Netbeans

Working on older versions of OTP

Older versions of OTP (the 0.11.x and 0.10.x branches) require significantly more plugins and configuration than the master branch. We encourage you to carry out development on the current master branch since we don't always have time to rebase bugfixes and patches between versions, and master will become our next relase. If for some reason you need to work with an older version, you will need to install a Lombok IDE plugin, import a multi-module Maven project, and possibly build OTP into a WAR package that is deployed to a Java application server.

There are also differences in the OpenTripPlanner web service URLs from one version to another. For more information, see Version-Notes.