| applyTo | description | |
|---|---|---|
|
Comprehensive best practices for adopting new Java 25 features since the release of Java 21. |
These instructions help GitHub Copilot assist developers in upgrading Java projects from JDK 21 to JDK 25, focusing on new language features, API changes, and best practices.
Primitive Types in Patterns, instanceof, and switch
When working with pattern matching:
- Suggest using primitive type patterns in switch expressions and instanceof checks
- Example upgrade from traditional switch:
// Old approach (Java 21)
switch (x.getStatus()) {
case 0 -> "okay";
case 1 -> "warning";
case 2 -> "error";
default -> "unknown status: " + x.getStatus();
}
// New approach (Java 25 Preview)
switch (x.getStatus()) {
case 0 -> "okay";
case 1 -> "warning";
case 2 -> "error";
case int i -> "unknown status: " + i;
}- Enable preview features with
--enable-previewflag - Suggest guard patterns for more complex conditions:
switch (x.getYearlyFlights()) {
case 0 -> ...;
case int i when i >= 100 -> issueGoldCard();
case int i -> ... // handle 1-99 range
}Replacing ASM with Standard API
When detecting bytecode manipulation or class file processing:
- Suggest migrating from ASM library to the standard Class-File API
- Use
java.lang.classfilepackage instead oforg.objectweb.asm - Example migration pattern:
// Old ASM approach
ClassReader reader = new ClassReader(classBytes);
ClassWriter writer = new ClassWriter(reader, 0);
// ... ASM manipulation
// New Class-File API approach
ClassModel classModel = ClassFile.of().parse(classBytes);
byte[] newBytes = ClassFile.of().transform(classModel,
ClassTransform.transformingMethods(methodTransform));JavaDoc Modernization
When working with JavaDoc comments:
- Suggest converting HTML-heavy JavaDoc to Markdown syntax
- Use
///for Markdown documentation comments - Example conversion:
// Old HTML JavaDoc
/**
* Returns the <b>absolute</b> value of an {@code int} value.
* <p>
* If the argument is not negative, return the argument.
* If the argument is negative, return the negation of the argument.
*
* @param a the argument whose absolute value is to be determined
* @return the absolute value of the argument
*/
// New Markdown JavaDoc
/// Returns the **absolute** value of an `int` value.
///
/// If the argument is not negative, return the argument.
/// If the argument is negative, return the negation of the argument.
///
/// @param a the argument whose absolute value is to be determined
/// @return the absolute value of the argumentRecord Enhancement
When working with records:
- Suggest using
withexpressions for creating derived records - Enable preview features for derived record creation
- Example pattern:
// Instead of manual record copying
public record Person(String name, int age, String email) {
public Person withAge(int newAge) {
return new Person(name, newAge, email);
}
}
// Use derived record creation (Preview)
Person updated = person with { age = 30; };Enhanced Stream Processing
When working with complex stream operations:
- Suggest using
Stream.gather()for custom intermediate operations - Import
java.util.stream.Gatherersfor built-in gatherers - Example usage:
// Custom windowing operations
List<List<String>> windows = stream
.gather(Gatherers.windowSliding(3))
.toList();
// Custom filtering with state
List<Integer> filtered = numbers.stream()
.gather(Gatherers.fold(0, (state, element) -> {
// Custom stateful logic
return state + element > threshold ? element : null;
}))
.filter(Objects::nonNull)
.toList();When detecting sun.misc.Unsafe usage:
- Warn about deprecated memory-access methods
- Suggest migration to standard alternatives:
// Deprecated: sun.misc.Unsafe memory access
Unsafe unsafe = Unsafe.getUnsafe();
unsafe.getInt(object, offset);
// Preferred: VarHandle API
VarHandle vh = MethodHandles.lookup()
.findVarHandle(MyClass.class, "fieldName", int.class);
int value = (int) vh.get(object);
// Or for off-heap: Foreign Function & Memory API
MemorySegment segment = MemorySegment.ofArray(new int[10]);
int value = segment.get(ValueLayout.JAVA_INT, offset);When detecting JNI usage:
- Warn about upcoming restrictions on JNI usage
- Suggest adding
--enable-native-accessflag for applications using JNI - Recommend migration to Foreign Function & Memory API where possible
- Add module-info.java entries for native access:
module com.example.app {
requires jdk.unsupported; // for remaining JNI usage
}When configuring garbage collection:
- Default ZGC now uses generational mode
- Update JVM flags if explicitly using non-generational ZGC:
# Explicit non-generational mode (will show deprecation warning)
-XX:+UseZGC -XX:-ZGenerational
# Default generational mode
-XX:+UseZGCWhen using G1GC:
- No code changes required - internal JVM optimization
- May see improved compilation performance with C2 compiler
When working with numerical computations:
- Suggest Vector API for SIMD operations (still incubating)
- Add
--add-modules jdk.incubator.vector - Example usage:
import jdk.incubator.vector.*;
// Traditional scalar computation
for (int i = 0; i < a.length; i++) {
c[i] = a[i] + b[i];
}
// Vectorized computation
var species = IntVector.SPECIES_PREFERRED;
for (int i = 0; i < a.length; i += species.length()) {
var va = IntVector.fromArray(species, a, i);
var vb = IntVector.fromArray(species, b, i);
var vc = va.add(vb);
vc.intoArray(c, i);
}For projects using preview features:
- Add
--enable-previewto compiler arguments - Add
--enable-previewto runtime arguments - Maven configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<release>25</release>
<compilerArgs>
<arg>--enable-preview</arg>
</compilerArgs>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<argLine>--enable-preview</argLine>
</configuration>
</plugin>- Gradle configuration:
java {
toolchain {
languageVersion = JavaLanguageVersion.of(25)
}
}
tasks.withType<JavaCompile> {
options.compilerArgs.add("--enable-preview")
}
tasks.withType<Test> {
jvmArgs("--enable-preview")
}- Update Build Tools: Ensure Maven/Gradle supports JDK 25
- Update Dependencies: Check for JDK 25 compatibility
- Handle Warnings: Address deprecation warnings from JEPs 471/472
- Enable Preview Features: If using pattern matching or other preview features
- Test Thoroughly: Especially for applications using JNI or sun.misc.Unsafe
- Performance Testing: Verify GC behavior with new ZGC defaults
When reviewing code for Java 25 upgrade:
- Replace ASM usage with Class-File API
- Convert complex HTML JavaDoc to Markdown
- Use primitive patterns in switch expressions where applicable
- Replace sun.misc.Unsafe with VarHandle or FFM API
- Add native-access permissions for JNI usage
- Use Stream gatherers for complex stream operations
- Update build configuration for preview features
- Test with
--enable-previewflag for preview features - Verify JNI applications work with native access warnings
- Performance test with new ZGC generational mode
- Validate JavaDoc generation with Markdown comments
- Preview Feature Dependencies: Don't use preview features in library code without clear documentation
- Native Access: Applications using JNI directly or indirectly may need
--enable-native-accessconfiguration - Unsafe Migration: Don't delay migrating from sun.misc.Unsafe - deprecation warnings indicate future removal
- Pattern Matching Scope: Primitive patterns work with all primitive types, not just int
- Record Enhancement: Derived record creation requires preview flag in Java 23
- ZGC generational mode may improve performance for most workloads
- Class-File API reduces ASM-related overhead
- Stream gatherers provide better performance for complex stream operations
- G1GC improvements reduce JIT compilation overhead
Remember to test thoroughly in staging environments before deploying Java 25 upgrades to production systems.