Sie sind auf Seite 1von 3

This software is OSI Certified Open Source Software.

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

1. Eclipse Project Release Notes


1. Target Operating Environments
2. Compatibility with Previous Releases
1. Compatibility of Release 4.14 with 4.13
3. Known Issues
1. General problems
2. General - Startup
1. Installation/Configuration issues that can cause Eclipse to fail start
2. Invalid characters in install directory prevents Eclipse from starting
3. Hanging during class loading when out of permanent generation
memory
3. General - GCJ
1. Problems with classloaders in created threads
2. Deadlock creating executable extension in Plugin.startup
3. Potential Problems Converting Plug-in Manifests
4. Location for Debug Options File on Mac OS
5. Issues with JNI that use FindClass
4. Platform - Ant
1. Custom Ant tasks and Ant types must be separate from plug-in
library JARs
2. XDoclet support from within Eclipse
3. Ant Editor code completion based on Ant 1.6.x
4. Setting build loggers not supported when debugging Ant builds
5. Renaming an External Tool builder set to run during auto-build
will cause errors
6. Slow typing/saving of the Ant editor with imports that define
numerous macrodefs
7. Ant 1.8.x reports missing libraries as build failures
5. Platform - User Assistance
1. Welcome page not displayed properly (Linux/Unix)
2. Help browser tool bar buttons do not work for some documents
3. Help documents not displayed in a browser or very slow document
loading (Windows only)
4. Working disconnected from the network (Windows only)
5. Using Internet Explorer in offline mode (Windows only)
6. Platform - UI
1. Dirty state not tracked properly for OLE documents (Windows
only)
2. OLE document crashes can cause Eclipse to also crash (Windows
only)
3. Toolbars only containing contributed controls exhibit display
errors on Mac/Linux
4. Allocating enough memory and solving OutOfMemoryError
5. Capabilities and Activities don't affect the menus and toolbars
7. Platform - SWT
1. Usage of swt.autoScale and GDK_SCALE flag on GTK platforms
2. Non-uniform scaling of text vs. icons when using intermediate
scaling factors on high-DPI displays
3. Eclipse plug-in based on the SWT Browser throws exception
4. Eclipse icon is duplicated in task-bar on Windows
5. BIDI Segments in Text controls
6. Block Selection functionality provided by StyledText is not BIDI
aware
8. Platform - Install/Update
1. Manually installing features and plug-ins on a FAT file system
(Windows only)
2. Connecting to untrusted sites using https
3. Extension location is lost if the install path changes
9. Java development tools (JDT)
1. Multiple regions formatting in a given source snippet
2. Searching for constant field references
3. Cut, copy, paste not working for linked resources in views showing
Java elements
4. Java working sets not working correctly for elements from JRE
system library container
5. Breakpoints unreliable running Sun 1.6.0_14
6. Suspend on uncaught exception overrides exception breakpoint
location filters
7. Running Java programs with non-Latin-1 characters in package or
class names
8. Cannot run or debug class in a project with GB18030 characters in
project name
9. Cannot detect installed JRE with GB18030 characters in path name
10. Cannot generate Javadoc for packages with GB18030 characters in
the name
11. Unable to debug stack overflows
12. Evaluation limitation
13. Missing debug attributes
14. Using Hot Code Replace
15. Scrapbook
16. Debugging over slow connections
17. Updating of inspected values
18. Stepping over native methods that perform I/O
19. Java Annotation Processing
20. Java indexing encounters problems when a folder is used both as a
source and a class folder
10. Plug-in Development Environment (PDE)
1. Feature manifest editor does not preserve all comments
2. PDE will not unzip source zips of some plug-ins
3. Emacs key bindings do not work in manifest editor fields
4. Export of plug-in may silently drop classes
5. Compilation errors when exporting projects not stored outside of
the workspace
6. Headless build needs to be run from a fully qualified path
7. Importing in Eclipse application fails if plug-in exists in host
workspace
8. Reusing a workspace after changing architectures silently breaks
PDE models
9. Missing @since tag API Tools problems on interface fields
containing @noreference tag

Das könnte Ihnen auch gefallen