### Eclipse Workspace Patch 1.0 #P org.eclipse.platform-feature Index: rootfiles/readme/readme_eclipse.html =================================================================== RCS file: /cvsroot/eclipse/org.eclipse.platform-feature/rootfiles/readme/readme_eclipse.html,v retrieving revision 1.106.2.5 diff -u -r1.106.2.5 readme_eclipse.html --- rootfiles/readme/readme_eclipse.html 25 Sep 2008 18:54:00 -0000 1.106.2.5 +++ rootfiles/readme/readme_eclipse.html 2 Jan 2009 22:39:54 -0000 @@ -3,14 +3,14 @@ -Eclipse Project Release Notes 3.4.1 +Eclipse Project Release Notes 3.4.2

Eclipse Project Release Notes

-

Release 3.4.1
- Last revised Sept 25, 2008

+

Release 3.4.2
+ Last revised January 5, 2008

This software is OSI Certified Open Source Software.
OSI Certified is a certification mark of the Open Source Initiative. 

@@ -1072,13 +1072,22 @@ extension location content to its original location (bug 232094).

-

Extension location is lost if the install path changes

+

Extension location is lost if the install path changes

A previously configured extension location may be temporarily removed if the install is moved or mounted under a different path. This only happens when the link file that configures the extension location uses a relative path that points to a directory under the Eclipse install. On a second startup using the same install path, the extension location is added again (bug 95403).

+

Feature patches can only be installed from Eclipse 3.4-based update sites

+

Feature patches can only be installed from update sites designed for Eclipse 3.4 or greater. +Specifically, the update site must have the necessary metadata for Equinox p2 (a content.xml +or content.jar file). This data can be generated by building an update site using Eclipse 3.4 +or newer, or running the p2 metadata generator on an update site built using earlier versions +of the Eclipse SDK. See the help topic Generating p2 metadata for more details on running the p2 metadata +generator (bug 244483). +

+

3.2.9 Platform - Debug

None. (Known problems with the Java debugger appear below in the JDT section.)