Eclipse class files not updating
This means that source files written to use Eclipse SDK 4.5 APIs might successfully compile and run against Eclipse SDK 4.6 APIs, although this is not guaranteed. If source files use new Eclipse SDK APIs, they will not be usable with an earlier version of the Eclipse SDK.
Workspace Compatibility: Eclipse SDK 4.6 is upwards workspace-compatible with earlier 3.x and 4.x versions of the Eclipse SDK unless noted.
Problems encountered when running Eclipse on a non-reference platform that cannot be recreated on any reference platform will be given lower priority than problems with running Eclipse on a reference platform.
Eclipse 4.6 is tested and validated on a number of reference platforms.
As such, the Eclipse SDK as a whole is targeted at all modern, desktop Java VMs.
We focus our testing on a handful of popular combinations of operating system and Java Platform; these are our .The Eclipse SDK supports GB 18030 (level 1), the Chinese code page standard, on Windows, Linux and the Macintosh. Eclipse 4.6 is compatible with Eclipse 4.5 (and all earlier 3.x versions).API Contract Compatibility: Eclipse SDK 4.6 is upwards contract-compatible with Eclipse SDK 4.5 except in those areas noted in the .JD-Core may be used to recover lost source code and explore the source of Java runtime libraries.New features of Java 5, such as annotations, generics or type “enum”, are supported. JD-Core, JD-GUI & JD-Eclipse are open source projects released under the GPLv3 License.
Non-compliant usage of API's: All non-API methods and classes, and certainly everything in a package with "internal" in its name or x-internal in the bundle manifest entry, are considered implementation details which may vary between operating environment and are subject to change without notice.