Keywords: Java class file | version numbers | compatibility errors | JVM specification | bytecode analysis
Abstract: This article provides an in-depth exploration of version numbering mechanisms in Java class file format, including definitions of major and minor versions, their roles, and positions within the Java Virtual Machine specification. By analyzing common UnsupportedClassVersionError occurrences, it explains the root causes of version incompatibility and presents a complete correspondence table between JDK versions and class file versions. The article combines official JVM specifications with practical code examples to detail how to inspect class file version information using bytecode tools and the impact of preview features on version numbering.
Fundamental Concepts of Java Class File Version Numbers
The Java class file format is a core component of the Java platform, where each compiled .class file contains specific version information. The version number consists of two parts: major version and minor version, formatted as <major>.<minor>. In the bytecode file, the major version is located at offset 7, while the minor version resides at offset 6.
Version Compatibility and Error Analysis
Java class files maintain backward compatibility but impose strict limitations on forward compatibility. When attempting to load a class file compiled for a higher Java version into a lower-version runtime environment, an UnsupportedClassVersionError exception is thrown. For instance, loading a Java 6-compiled class file in a Java 5 runtime produces the error: "incompatible class version, got 50, expected 49". Here, 50 represents Java 6's major version, and 49 denotes Java 5's major version.
Complete Version Correspondence Table
The following table provides the complete mapping between JDK versions and class file versions:
<table> <thead> <tr><th>JDK Version</th><th>Class File Version</th></tr> </thead> <tbody> <tr><td>Java 1.0.2</td><td>45.0</td></tr> <tr><td>Java 1.1</td><td>45.3</td></tr> <tr><td>Java 1.2</td><td>46.0</td></tr> <tr><td>Java 1.3</td><td>47.0</td></tr> <tr><td>Java 1.4</td><td>48.0</td></tr> <tr><td>Java 5</td><td>49.0</td></tr> <tr><td>Java 6</td><td>50.0</td></tr> <tr><td>Java 7</td><td>51.0</td></tr> <tr><td>Java 8</td><td>52.0</td></tr> <tr><td>Java 9</td><td>53.0</td></tr> <tr><td>Java 10</td><td>54.0</td></tr> <tr><td>Java 11</td><td>55.0</td></tr> <tr><td>Java 12</td><td>56.0</td></tr> <tr><td>Java 13</td><td>57.0</td></tr> <tr><td>Java 14</td><td>58.0</td></tr> <tr><td>Java 15</td><td>59.0</td></tr> <tr><td>Java 16</td><td>60.0</td></tr> <tr><td>Java 17</td><td>61.0</td></tr> <tr><td>Java 18</td><td>62.0</td></tr> <tr><td>Java 19</td><td>63.0</td></tr> <tr><td>Java 20</td><td>64.0</td></tr> <tr><td>Java 21</td><td>65.0</td></tr> <tr><td>Java 22</td><td>66.0</td></tr> </tbody>Preview Features and Special Version Handling
For class files utilizing preview features, the minor version is set to 65535. This special version configuration restricts the loading scope of class files: they can only be loaded in JDK versions matching the major version, and even newer JDK versions are prohibited from loading such files. This mechanism effectively controls the experimental nature of preview features.
Practical Applications and Tool Usage
Developers can inspect class file version information through various tools. Using the javap command allows detailed analysis of class file structure:
javap -verbose MyClass.classLocate the "major version" and "minor version" fields in the output to obtain accurate version information. Additionally, specialized bytecode analysis tools like JD-GUI and Bytecode Viewer can be used for visual inspection.
Specification References and Authoritative Sources
The official specification for Java class file format is defined in Chapter 4, "The class File Format," of the Java Virtual Machine specification. Oracle's official documentation provides the most authoritative reference for version information, and developers are advised to consult it first when encountering version compatibility issues. Community resources like Wikipedia also offer practical reference information, particularly regarding historical version correspondences.