blob: f568c133d2521852aabbe82ea5eed13b43f25010 [file] [log] [blame]
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Author" content="IBM">
<meta name="GENERATOR" content="Mozilla/4.75 [en] (WinNT; U) [Netscape]">
<title>Java Debug Release Notes</title>
<h1>Eclipse 3.5 Java Debug Build Notes</h1>
<h2>Summary of API changes in 3.5</h2>
<h3>Configurable problem severity when a compatible JRE cannot be bound to specified execution environment </h3>
<p><strong>Description:</strong> In release 3.4 and earlier, when a project was bound to an execution environment (for example, J2SE-1.4), and the workspace did not have a strictly compatible JRE installed (for example, only a J2SE-1.5 JRE was available), a build path problem with a warning severity was issued. Since 3.5, API has been added to allow the severity of the problem to be ignored, a warning, or an error. See the newly added constants in JavaRuntime: <code>PREF_STRICTLY_COMPATIBLE_JRE_NOT_AVAILABLE</code>, <code>VALUE_IGNORE</code>, <code>VALUE_WARNING</code>, and <code>VALUE_ERROR</code>.</p>
<h3>OSGi Profile Properties for IExecutionEnvironment </h3>
<p><strong>What is affected:</strong> Clients contributing an execution environment can provide an associated OSGi system profile properties file. </p>
<p><strong>Description:</strong> In release 3.4 and earlier, clients could contribute an execution environment, but when that environment was bound to a build path for a plug-in project, default compiler compliance settings were not set appropriately. Since 3.5, clients may specify an OSGi system profile properties file with an execution environment. The properties file provides information about system packages, default source and target compiler settings, etc. When provided, tooling will be able to leverage the information to create default access rules for system packages and properly set default compiler compliance settings for projects bound to the contributed environment. See the newly added method <code>IExecutionEnvironment.getProfileProperties()</code> and the new extension point attribute <code>profileProperties</code>.</p>
<p><strong>Action required:</strong> Clients contributing an execution environment should provide an associated OSGi system profile properties file. </p>
<h2>August 26, 2008</h2>
<h3>Problem Reports Fixed</h3>
<a href="">Bug 189486</a>: Unable to retrieve system properties for 1.1.8 VM<br>
<a href="">Bug 245153</a>: Variable references empty selection: ${java_type_name}<br>
<h2>October 7, 2008</h2>
<h3>Problem Reports Fixed</h3>
<a href="">Bug 248466</a>: Cannot launch if build path contains a &quot;..&quot; entry<br>
<a href="">Bug 244693</a>: Default severity for missing JRE for Execution Environment should be Error<br>
<a href="">Bug 249490</a>: JDI fails to unmarshal JDWP reply packet correctly<br>
<h2>August 19, 2008</h2>
<h3>Problem Reports Fixed</h3>
<a href="">Bug 244285</a>: An internal error occurred during: &quot;Initializing Java Tooling&quot;.<br>
<h2>3.5 M1 - August 8, 2008</h2>
<h3>Problem Reports Fixed</h3>
<a href="">Bug 238350</a>: Starting Java application (like JBoss) in debug causes NPE. Run mode works ok<br>
<h2>July 8, 2008</h2>
<h3>Problem Reports Fixed</h3>
<a href="">Bug 239612</a>: Use Ctrl+Click instead of Ctrl+Alt for 'Step Into Selection'<br>
<h2>August 12, 2008</h2>
<h3>Problem Reports Fixed</h3>
<a href="">Bug 217752</a>: [logview] provide action to open entry stack trace in console<br>