-
Notifications
You must be signed in to change notification settings - Fork 172
Changes in Force.com IDE Beta Version 37.0.0.20160512
To install the beta version of the Force.com IDE, follow these instructions: Downloading the Beta Version of the Force.com IDE
Changes in the sandbox-release beta version of Force.com IDE v37.0 include the following.
We’ve updated the Force.com IDE to require Java 8 and Eclipse 4.5 (Mars) or later. Most of you have switched to these technologies. Focusing on them enables us to optimize your experience with our tools. As we announced in November 2015, Salesforce is disabling the TLS 1.0 encryption protocol to increase security. TLS 1.0 is disabled by default in Java 8, which also includes other security fixes.
We’ve enabled Eclipse’s Open Type functionality for Apex types. You can now open a dialog to search your Apex classes and triggers by pressing Ctrl+Shift+T (Cmd+Shift+T on OS X) or choosing Navigate | Open Apex Type.
This functionality is available only in the Force.com perspective. For more information, see Open Type in the Eclipse documentation.
You can now set breakpoints on System and custom exceptions. When an exception on which you’ve set a breakpoint is thrown during a debugging session, execution halts. The Apex Debugger pauses on the line of code that caused the thrown exception.
To set an exception breakpoint, from the Breakpoints pane in the Debug perspective, click Add Apex Breakpoint. A list of all exceptions in your workspace displays. Select an exception, confirm that the exception’s listed project is the project you’re working in, and then click Set Breakpoint.
You can now change the names of test methods that are included in full-class test run configurations and then execute test runs without errors. Previously, if you changed a test method’s name after setting up a test run configuration that included the method’s class, the Force.com IDE could execute the run configuration only after you updated the configuration. You still need to update run configurations that contain individual test methods when you change the methods’ names. This fix is only for run configurations that contain full classes, including run configurations that execute all tests in your org.