Update to ASM 9.10.1 (Java 27 support)

[SougandhS]

Fixes : #955

What it does

How to test

Author checklist

• I have thoroughly tested my changes
• The change is following the coding conventions
• I have signed the Eclipse Contributor Agreement (ECA)

[iloveeclipse]

I assume build will fail, we need to wait for eclipse-platform/eclipse.platform.releng.aggregator#3823 / 4.41 release start

[merks]

FYI, I'm hoping that a new ASM 9.10.1 and compatible jacoco arrive this week. But it's beyond my control...

[iloveeclipse]

FYI, I'm hoping that a new ASM 9.10.1 and compatible jacoco arrive this week. But it's beyond my control...

I would not update in 4.40. I guess we will need Xtext update as well, it is too late now.

What wonders me more is why this PR build doesn't fail? I assumed we consume ASM from target platform?

[SougandhS]

What wonders me more is why this PR build doesn't fail? I assumed we consume ASM from target platform?

Issue with my jar ?

[iloveeclipse]

Issue with my jar ?

No, I mean, the build shouldn't work because it shouldn't be able to "see" ASM in 9.10 version yet because IMO it should be resolved via platform target which doesn't have it yet: https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/pull/3823/changes

[SougandhS]

Updated to ASM 9.10.1

[eclipse-jdt-bot]

This pull request changes some projects for the first time in this development cycle.
Therefore the following files need a version increment:

org.eclipse.jdt.launching/META-INF/MANIFEST.MF
org.eclipse.jdt.launching/pom.xml

An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch.

Git patch

From 7ce7086eb3975e78f799ca3f1c5330e97f0b4263 Mon Sep 17 00:00:00 2001
From: Eclipse JDT Bot <jdt-bot@eclipse.org>
Date: Sat, 30 May 2026 12:35:46 +0000
Subject: [PATCH] Version bump(s) for 4.41 stream


diff --git a/org.eclipse.jdt.launching/META-INF/MANIFEST.MF b/org.eclipse.jdt.launching/META-INF/MANIFEST.MF
index 3a986e897..400b0bfb7 100644
--- a/org.eclipse.jdt.launching/META-INF/MANIFEST.MF
+++ b/org.eclipse.jdt.launching/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %pluginName
 Bundle-SymbolicName: org.eclipse.jdt.launching; singleton:=true
-Bundle-Version: 3.24.200.qualifier
+Bundle-Version: 3.24.300.qualifier
 Bundle-Activator: org.eclipse.jdt.internal.launching.LaunchingPlugin
 Bundle-Vendor: %providerName
 Bundle-Localization: plugin
diff --git a/org.eclipse.jdt.launching/pom.xml b/org.eclipse.jdt.launching/pom.xml
index c1dd74031..e9baa0b9a 100644
--- a/org.eclipse.jdt.launching/pom.xml
+++ b/org.eclipse.jdt.launching/pom.xml
@@ -18,7 +18,7 @@
   </parent>
   <groupId>org.eclipse.jdt</groupId>
   <artifactId>org.eclipse.jdt.launching</artifactId>
-  <version>3.24.200-SNAPSHOT</version>
+  <version>3.24.300-SNAPSHOT</version>
   <packaging>eclipse-plugin</packaging>
   
   <build>
-- 
2.54.0

Further information are available in Common Build Issues - Missing version increments.

[SougandhS]

Hi @iloveeclipse, could you please check this ?

[merks]

FYI, the change to use 9.10.1 in the target platform for 4.41 master is merged.