Developing the LDSTech IDE

This page is meant to be a resource for anyone who wants to work on the LDSTech IDE and its plugins itself. If you just want to use the LDSTech IDE refer to Getting started with the LDSTech Java WebApp Platform instead. To get the IDE build working locally, you will need Java 1.7 and Maven 3. The following steps will help you get the IDE build working in Eclipse:

  1. Download a basic version of Eclipse. You can get the base Java version or the JEE version. The latter is the largest and includes a lot of unnecessary stuff, but it does include a lot of plugins we use and may save you some time. Make sure you download the version you are interested in developing against. NOTE: It is NOT recommended to use a pre-existing LDSTech IDE installation as the base for your IDE build environment.
  2. You'll need to install Subclipse, m2eclipse, and m2eclipse-tycho to get the most basic functionality. You'll generally want to get the latest versions of these, but m2eclipse and Subclipse can be installed via the thirdparty dev update site. m2eclipse-tycho should be installed from Sonatype's nightly build repository.
  3. You'll also want to install any other 3rd party plugins that are part of the IDE build. This includes Spring IDE/STS, the GWT plugin, WTP (if you didn't download the JEE distribution), the DTP plugin, and a few others. This is kind of a trial-and-error process - if a project is marked with an error because a plugin cannot be found, it is pretty easy to figure out which plugin you need and install it.
  4. Checkout the project and import it as a Maven project, just like you would any other Maven-based project.
  5. You can launch a workspace by going to Run > Run Configurations... and creating a new Eclipse Application launch configuration. It shouldn't need to be customized.

A few helpful hints:

  1. The sources for a lot of plugins are available via update sites. Look for features with 'SDK' in them - that usually implies a source bundle. In many cases, you'll have to find and add the project-specific update site to get the sources, however, as they aren't included in the Indigo site.
  2. When you first install the base Eclipse, make sure you specify a JDK and up the memory (both Xmx and PermGen sizes).
  3. One helpful option in the Run configuration is Workspace Data > 'Clear: workspace'. Also, leave 'Ask for confirmation before clearing' checked. This allows you to clear the workspace on startup when you want, which can be helpful for testing and development.
  4. A lot of this process is hard to define and may change over time - patience is really helpful when it comes to Eclipse builds :)
This page was last modified on 4 October 2011, at 14:03.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.