From 655dd1cdccc0f56f72e2f91ed59d3a00b63d6710 Mon Sep 17 00:00:00 2001
From: Alexander Kriegisch <Alexander@Kriegisch.name>
Date: Fri, 15 Dec 2023 12:14:44 +0700
Subject: [PATCH] Compile to target 17

This should avoid the strange "NoSuchFieldError: RELEASE_17" error
message in AJC.

Relates to eclipse-aspectj/aspectj#269.

Signed-off-by: Alexander Kriegisch <Alexander@Kriegisch.name>
---
 org.eclipse.jdt.core/pom.xml | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/org.eclipse.jdt.core/pom.xml b/org.eclipse.jdt.core/pom.xml
index ba065f83e0..da0f643606 100644
--- a/org.eclipse.jdt.core/pom.xml
+++ b/org.eclipse.jdt.core/pom.xml
@@ -174,12 +174,9 @@
     <!-- Basic build properties -->
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
     <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
-    <!--
-      Eclipse JDT Core now requires Java 17 and has started using more recent source code constructs.
-      At least for now, compiling to target 11 ist still possible.
-    -->
+    <!-- Eclipse JDT Core now requires Java 17 -->
     <maven.compiler.source>17</maven.compiler.source>
-    <maven.compiler.target>11</maven.compiler.target>
+    <maven.compiler.target>17</maven.compiler.target>
 
     <!-- By default, deploy this public artifact -->
     <maven.deploy.skip>false</maven.deploy.skip>