Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mat-dev] Could we make Java 21 a requirement for the next MAT release?
  • From: KEVIN GRIGORENKO <kevin.grigorenko@xxxxxxxxxx>
  • Date: Fri, 17 Jan 2025 16:53:10 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=us.ibm.com; dmarc=pass action=none header.from=us.ibm.com; dkim=pass header.d=us.ibm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=i+aT78v+WYUn71VBxfuqLJjXy4c77GY9atgkSECpYZI=; b=un4HKoLiK50HjL/HiYYHBW12zJGVP5VUcv2NprVXmWU5mFZDEnl2iUX484c+3bZUU4KDEmduhxdDOTEpZB99/bezTcxb9+uFFlbsoquIJ6hDSXrGii4aI6m18lz1u/kLgcSNibGJw5BkVuV3lzbRZfaQV0+VcGsTdSDuazHRab1EIyOTVMdlyCa30lFChmxu2te8d6yK/Jr7AvGXf0z8/miMSbuY7h2a5qfflAObKwnv3tnxTBBHGji0onvvT2FOByVjOMJXGmCBVQUGGFKF9VPlUjb3mO6pT/OzBN35ZvZfwwMX5kHuFj5dFUM+L9gQx2ilprWscypWn4LOjPPFkw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=Cy40ck5suOwLfcjhu8K4zqLbuypJyEzuMCa62KjcGXmpZf448YhjOBB7S17mSkF3yA4AMCyLiUhAXZtO8whoIGsR8dIM6ViMEc7/2YQPW900Ha3jgupbGt2+Kbi9H6fNw/iBJW/EFQ6D001Dn55y28CTDXA2+4Saqf7xMFau05oh3CnmFJbSTNCqsZPbYbe8/n9bZ34MZFpmsPSK4zw0LRCkUrh5igW2V1EIcVScrax8PBXwFfWxvl1j2vPXPtroSgLkSuCQVLEdxIBsTftC0sfw3stiP1BpVzYoExPI9BOmm/CQJ+HNMmOG/V49dxkmHjJqDG0vO3GUw5b3QOx7fw==
  • Delivered-to: mat-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/mat-dev/>
  • List-help: <mailto:mat-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/mat-dev>, <mailto:mat-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/mat-dev>, <mailto:mat-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHbaLGxuS9xL31OuU2usJi+SJtzdrMbLb/5
  • Thread-topic: Could we make Java 21 a requirement for the next MAT release?

Hey Krum,

 

I agree, the standalone MAT should require whatever the latest Eclipse requires. I just searched and we don’t specify maven.compiler.source or maven.compiler.target properties in pom.xml so is the compiler version chosen based on Bundle-RequiredExecutionEnvironment in MANIFEST.MF, or is it just chosen by whatever version of the compiler is used on the build machine? In my opinion, unless there’s a need to increase the compiler version for MAT development, it would be nice to build MAT with Java 8 so that users could continue to add the MAT update site to older Eclipse builds and Java 8 is currently the oldest LTS release.

 

-- 

Kevin Grigorenko

Application Runtimes SWAT, IBM Software Support

 

 

From: mat-dev <mat-dev-bounces@xxxxxxxxxxx> on behalf of Tsvetkov, Krum via mat-dev <mat-dev@xxxxxxxxxxx>
Date: Friday, January 17, 2025 at 2:03 AM
To: Memory Analyzer Dev list <mat-dev@xxxxxxxxxxx>
Cc: Tsvetkov, Krum <krum.tsvetkov@xxxxxxx>
Subject: [EXTERNAL] [mat-dev] Could we make Java 21 a requirement for the next MAT release?

Hi, I am looking for feedback on how to deal with the minimal Java version required for standalone MAT. End of last year there was a post on the cross-projects list [1] which (if I understand it correctly) announced that the starting with the

Hi,

 

I am looking for feedback on how to deal with the minimal Java version required for standalone MAT.

 

End of last year there was a post on the cross-projects list [1] which (if I understand it correctly) announced that the starting with the 2025-03 release the Eclipse Platform will require Java 21. This would mean that once we start using this version as the basis for standalone MAT, we’d also require Java 21.

 

In the past MAT has been rather conservative, trying to keep the Java requirement as low as possible - knowing that many of the corporate customers are still using relatively old java versions. However, my current thinking is that:

  • It is good to stick to the latest platform and if it requires a newer Java, then also MAT should require it. Not because of new functionality - I believe MAT could work just fine not utilizing the new platform features, but we need to pick updated dependencies – otherwise CVEs accumulate, and it becomes difficult to include the standalone MAT in a product where strict policies apply
  • Users who cannot use a newer JDK still have the possibility to use an older standalone MAT or install the MAT features into an older Eclipse installation.

 

What are your thoughts on this?

 

Regards,

Krum

 

[1] https://www.eclipse.org/lists/cross-project-issues-dev/msg20005.html

Back to the top