-
Notifications
You must be signed in to change notification settings - Fork 133
feat: update eclipse platform to 26-09 #1502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sigmaaa
wants to merge
3
commits into
master
Choose a base branch
from
eclipse_platform_update_26_09
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| -Djdk.xml.maxGeneralEntitySizeLimit=0 | ||
| -Djdk.xml.maxParameterEntitySizeLimit=0 | ||
| -Djdk.xml.totalEntitySizeLimit=0 | ||
| -Djdk.xml.entityExpansionLimit=0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: espressif/idf-eclipse-plugin
Length of output: 166
🏁 Script executed:
Repository: espressif/idf-eclipse-plugin
Length of output: 6545
🏁 Script executed:
Repository: espressif/idf-eclipse-plugin
Length of output: 6486
🌐 Web query:
Eclipse OSGi -Dosgi.requiredJavaVersion runtime option minimum Java version💡 Result:
There is no single "minimum" Java version for the Eclipse OSGi runtime (Equinox) as a whole; rather, the required Java version is determined at the bundle level and depends on the specific version of the Eclipse SDK or Equinox framework being used [1][2]. Key technical points regarding Eclipse OSGi/Equinox and Java requirements: 1. Bundle-Level Requirements: In the OSGi ecosystem, individual bundles specify their minimum required Java version using the Bundle-RequiredExecutionEnvironment (BREE) header in their MANIFEST.MF file [1][3]. The Equinox runtime will refuse to resolve or run a bundle if the running Java Runtime Environment (JRE) does not meet the minimum environment specified by that bundle [1]. 2. Evolution of Requirements: The minimum requirements for Eclipse SDK components are updated periodically [2]. When developing or running applications on top of the Eclipse/Equinox platform, you must ensure your JRE meets or exceeds the highest BREE requirement of all bundles in your target platform [1]. 3. Modern Context: As of September 2026, the Eclipse ecosystem has moved to support much newer Java versions, with Eclipse releases like the 2026-03 (4.39) and 2026-06 (4.40) versions providing support for Java 26 [4][5]. Development and build processes for the Eclipse platform itself are frequently updated to target these newer Java versions (e.g., preparations for support of Java 25 and beyond) [6][7]. For developers, the best practice is to set the BREE to the smallest Execution Environment that provides the features your bundle requires to maximize adoption [1]. If you are working with a specific version of the Eclipse SDK, you should check the official release notes or the MANIFEST.MF files of the core bundles to determine the specific minimum JRE required for that release [8][2].
Citations:
🌐 Web query:
site:github.com/eclipse-equinox/equinox "osgi.requiredJavaVersion"💡 Result:
There is no standard OSGi property named osgi.requiredJavaVersion in the OSGi core framework specification [1]. In OSGi, requirements regarding the Java environment are typically handled using Execution Environments [2]. The standard mechanisms for specifying Java version requirements include: 1. Bundle-RequiredExecutionEnvironment (BREE): This manifest header specifies the execution environments required by a bundle (e.g., JavaSE-1.8) [2][3]. 2. Capability and Requirement Model: OSGi frameworks represent Java environments as capabilities (osgi.ee) [4]. Bundles can declare requirements on these capabilities using the Require-Capability header, which allows for more granular filtering by version [4]. If you are encountering osgi.requiredJavaVersion, it is likely a non-standard or custom property specific to a particular application, build tool, or framework implementation, rather than a part of the official OSGi specification [1].
Citations:
🌐 Web query:
Eclipse source "osgi.requiredJavaVersion" "required Java version"💡 Result:
The osgi.requiredJavaVersion property is an Eclipse runtime option that specifies the minimum Java version required to launch an Eclipse-based application [1][2]. If the Java Runtime Environment (JRE) detected at startup does not meet or exceed the version specified by this argument, the application will fail to start and typically display an "Incompatible JVM" error dialog [3]. Key points regarding osgi.requiredJavaVersion: - Configuration: It is commonly defined in the eclipse.ini file of an Eclipse distribution [3][4]. - Default Value: If not explicitly set, the default value is "1.4.1" [1][2]. - Usage: It serves as a guardrail to ensure that the environment has the necessary Java capabilities to run the bundled plugins or product features [3]. - Behavior: When the required version is not met, the Eclipse launcher identifies the mismatch before full initialization and alerts the user, providing a cleaner feedback mechanism than a crash later in the loading process [3]. When troubleshooting startup issues related to this setting, it is important to ensure that the -vm argument in the eclipse.ini file (which points to the specific Java executable) is set correctly and appears before the -vmargs line [4]. The osgi.requiredJavaVersion value must be compatible with the JRE pointed to by the -vm argument [4].
Citations:
🌐 Web query:
site:help.eclipse.org/latest/topic/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html osgi.requiredJavaVersion💡 Result:
osgi.requiredJavaVersionis an Eclipse runtime system property intended to specify the minimum Java version required to launch Eclipse. However, the current Eclipse documentation states that its default istrueand that it only takes effect whenosgi.signedcontent.support=certificate—wording that appears unusual and may reflect legacy documentation. (help.eclipse.org)Citations:
Set both
osgi.requiredJavaVersionarguments to25.Eclipse uses this property as the minimum Java version for launching. The product descriptor and selected
JavaSE-25container require Java 25, but this configuration still declares Java 11 twice. Update both values to25.🤖 Prompt for AI Agents
Source: MCP tools