Install the Developer Studio features in Eclipse

Prerequisites

Before you install Developer Studio features in Eclipse, make sure you have:

• Java 21.
• OpenEdge 13.1.
• The Developer Studio license: Install the Progress Developer Studio for OpenEdge component from the OpenEdge 13.1 installer. This component provides the required license.
• The Feature Repository: Confirm that the Feature Repository (Architect_Repo) is available at %DLC%\oeide.
• A supported Eclipse IDE: Developer Studio supports Eclipse 4.38, 4.39, or 4.40. You can use either the Eclipse Platform binary or the Eclipse SDK binary. Both support Developer Studio, and the installation steps are the same. You can choose:
  • Eclipse Platform if you use Eclipse primarily for Developer Studio.
  • Eclipse SDK if you plan to use Developer Studio and also need the additional Eclipse development tools included with the SDK.

For your Eclipse version, identify a matching Orbit repository URL. You can use either of the two URLs listed for that version.

Install Developer Studio only with an OpenEdge, Eclipse, and Java combination supported for your release. Refer to the Progress Compatibility Guide for current compatibility information.

Install the Developer Studio features

You can install the Developer Studio features using either of the following methods:

Install using the Eclipse IDE

1. Open Eclipse IDE and select Help > Install New Software from Eclipse menu.

   The Available Software wizard appears.

2. Click Add.

   The Add Repository window appears.

3. To add the corresponding Eclipse Orbit repository for the installed Eclipse version:
   1. In the Name field, type a name for the Orbit repository, such as Eclipse Orbit.
   2. Copy one of the two Orbit URLs listed for your Eclipse version in the preceding table, and paste it into the Location field.
   3. Click Add.
   Note: You do not need to install Orbit separately. Simply add the Orbit repository to your Eclipse configuration. Installing Orbit separately can lead to dependency version mismatches.
4. To add the Developer Studio Feature Repository, click Add in the Available Software wizard.

   The Add Repository window appears again.

   1. In the Name field, type a descriptive label, such as Feature Repository.
   2. Click Local, and browse to %DLC%\oeide to select the Architect_Repo repository supplied with the OpenEdge installer.
   3. Click Add.
5. In the Available software wizard, confirm that all configured repositories are enabled and available for dependency resolution. Then select Progress Developer Studio for OpenEdge and click Next. For air-gapped environments, use the approved offline dependency arrangement for the target release.

   The Install Details page of Available Software appears.

6. Review the features to be installed and click Next.

   The Review Licenses page of Available Software appears.

7. To start installation, accept the terms of the license agreements and click Finish.
8. If Eclipse displays an unsigned-content warning in the Trust Artifacts window, review the listed content, click Select All and then click Trust Selected as required by the security policy of your organization.
9. To complete installation of the Developer Studio features, restart Eclipse when prompted.
10. Go to Help > About Eclipse Platform > Installation Details and in the Installed Software tab, confirm that Progress Developer Studio for OpenEdge appears in the list.

Install using the command line

To install the Developer Studio features into a supported Eclipse installation, run the following command from Command Prompt or Proenv. Replace each value represented by %...% with the appropriate path or value for your environment.

To install the Developer Studio features into an existing, supported Eclipse installation, run the following command from Command Prompt or Proenv. The command uses the Eclipse p2 director to install the Developer Studio features into the Eclipse installation specified by %ECLIPSE_HOME%. Replace each value represented by %...% with the appropriate path or value for your environment.

"%ECLIPSE_EXE%" -nosplash -application org.eclipse.equinox.p2.director -repository "%PDSOE_P2_REPO%,%ECLIPSE_P2_REPO%,%GEF_P2_REPO%,%ORBIT_P2_REPO%" -installIU com.openedge.pdt.feature.group -destination "%ECLIPSE_HOME%" -profileProperties org.eclipse.update.install.features=true -p2.os win32 -p2.ws win32 -p2.arch x86_64 > "%STDOUT_FILE%" 2> "%STDERR_FILE%"

Where:

• %ECLIPSE_EXE%: Full path to eclipse.exe in the Eclipse installation used to perform the Developer Studio installation.
• %PDSOE_P2_REPO%: Location of the PDSOE p2 repository, made available through the OpenEdge installation at %DLC%\oeide.
• %DLC%: The OpenEdge installation directory.
• %ECLIPSE_P2_REPO%: URL of the Eclipse release repository that corresponds to the Eclipse version being used. For example, you need to provide https://download.eclipse.org/releases/2026-06.
• %GEF_P2_REPO%: URL of the Eclipse GEF repository, for example: https://download.eclipse.org/tools/gef/classic/release/3.22.0/.
• %ORBIT_P2_REPO%: URL of the Eclipse Orbit repository that corresponds to the Eclipse version being used. For example: https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/2026-06.
• %ECLIPSE_HOME%: Full path to the target Eclipse installation into which the Developer Studio features are installed.
• %STDOUT_FILE%: File that receives standard output from the Eclipse p2 director while it installs the Developer Studio features into the target Eclipse installation.
• %STDERR_FILE%: File that receives error output from the Eclipse p2 director during the Developer Studio feature installation.
• -vm: Specifies the Java run time that Eclipse uses for the command. The path specified with -vm must point to a supported Java executable.
• -repository: Specifies the Developer Studio, Eclipse release, GEF, and Eclipse Orbit repositories used to resolve dependencies.
• -installIU: Specifies the Developer Studio feature to be installed.
• -destination: Specifies the target Eclipse installation.

For example, use one of the following commands, depending on the Java runtime configured for the command environment.

• If Java 21 is already configured for the command environment, run:

  "C:\Progress\OpenEdge\oeide\eclipse_440\eclipse\eclipsec.exe" -nosplash -application org.eclipse.equinox.p2.director -repository "file:///C:/Progress/OpenEdge/oeide,https://download.eclipse.org/releases/2026-06,https://download.eclipse.org/tools/gef/classic/release/3.22.0/,https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/2026-06" -installIU com.openedge.pdt.feature.group -destination "C:\Progress\OpenEdge\oeide\eclipse_440\eclipse" -profileProperties org.eclipse.update.install.features=true -p2.os win32 -p2.ws win32 -p2.arch x86_64 1>"C:\Progress\OpenEdge\oeide\eclipse_440\p2-director-stdout.txt" 2>"C:\Progress\OpenEdge\oeide\eclipse_440\p2-director-stderr.txt"

• If the configured Java version is earlier than Java 21, copy a supported Java 21 run time into the JRE folder inside the Eclipse installation, and specify that run time with the -vm option:

  "C:\Progress\OpenEdge\oeide\eclipse_440\eclipse\eclipsec.exe" -vm "C:\Progress\OpenEdge\oeide\eclipse_440\eclipse\JRE\bin\javaw.exe" -nosplash -application org.eclipse.equinox.p2.director -repository "file:///C:/Progress/OpenEdge/oeide,https://download.eclipse.org/releases/2026-06,https://download.eclipse.org/tools/gef/classic/release/3.22.0/,https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/2026-06" -installIU com.openedge.pdt.feature.group -destination "C:\Progress\OpenEdge\oeide\eclipse_440\eclipse" -profileProperties org.eclipse.update.install.features=true -p2.os win32 -p2.ws win32 -p2.arch x86_64 1>"C:\Progress\OpenEdge\oeide\eclipse_440\p2-director-stdout.txt" 2>"C:\Progress\OpenEdge\oeide\eclipse_440\p2-director-stderr.txt"

Post-installation validation and configuration checklist

1. After the installation is complete, review the generated standard-output and standard-error log files for installation progress, completion messages, errors, and warnings. The 1> redirect writes standard output to the specified standard-output log file, and the 2> redirect writes error output to the specified standard-error log file. In the sample command, the logs are located at <output_log_path> and <error_log_path>.
2. If Eclipse starts but reports errors, review the Eclipse error log from Window > Show View > Error Log. You can also review the workspace log at <workspace>\.metadata\.log.
3. Complete the following configuration and validation steps:
   1. Switch to the OpenEdge Editor perspective.
   2. To use Progress keyboard shortcuts, select Progress Scheme in Window > Preferences > General > Keys.
   3. Verify DLC detection by selecting Window > Preferences > OpenEdge.
   4. Configure the Class Browser engine for Eclipse 4.38, 4.39, or 4.40 using one of the following:
      • Install the Microsoft Edge WebView2 Runtime if it is not already available.
      • If Eclipse displays the Default browser engine not available dialog, select Use IE. Then reopen Class Browser. Eclipse restarts and you may need to select Use IE again when the dialog box appears.
   5. Confirm the installed version by selecting Help > About Eclipse IDE > Installation Details.
   6. Confirm that the expected Developer Studio functionality is available.