Eclipse class files not updating
Eclipse undoubtedly runs fine in many operating environments beyond the reference platforms we test.
However, since we do not systematically test them we cannot vouch for them.
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 .
The “Java Decompiler project” aims to develop tools in order to decompile and analyze Java 5 “byte code” and the later versions.
Source Compatibility: Eclipse SDK 4.6 is upwards source-compatible with Eclipse SDK 4.5 except in the areas noted in the .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.Client plug-ins that directly depend on anything other than what is specified in the Eclipse SDK API are inherently unsupportable and receive no guarantees about compatibility within a single release much less with earlier releases.Programs that use affected APIs and extension points will need to be ported to Eclipse SDK 4.6 APIs. There is no guarantee that compliance with Eclipse SDK 4.6 APIs would ensure compliance with Eclipse SDK 4.5 APIs.
Refer to for a discussion of the kinds of API changes that maintain contract compatibility.JD-Core may be used to recover lost source code and explore the source of Java runtime libraries.