-
Notifications
You must be signed in to change notification settings - Fork 134
IEP-1727: Update target platform to Eclipse 2026-03 (4.39) #1415
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
IEP-1727
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 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
Some comments aren't visible on the classic Files Changed page.
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
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.
🧩 Analysis chain
🏁 Script executed:
Repository: espressif/idf-eclipse-plugin
Length of output: 3603
🌐 Web query:
What API changes were made in Eclipse LSP4E 0.30.0 release?💡 Result:
The Eclipse LSP4E 0.30.0 release (February 11, 2026) includes the following API changes: - Adaptation to LSP4J version 1.0.0 (PR
#1421), which itself has breaking changes such as removal of deprecated APIs, convenience constructors, properties in FormattingOptions, static methods in Either class, and websocket bundle deprecation. - Breaking change: Refactor to get rid of some deprecated APIs (PR#1496by FlorianKroiss). Specific details on which APIs were removed or refactored are not explicitly listed in the release notes, but it is highlighted under "Breaking changes" in the official GitHub release page. No other explicit public API changes are mentioned in the release notes. The full changelog from 0.29.5 to 0.30.0 can be viewed on GitHub.Citations:
🏁 Script executed:
# Check full LspService.java content to see `@SuppressWarnings` and method usages cat -n bundles/com.espressif.idf.core/src/com/espressif/idf/core/util/LspService.javaRepository: espressif/idf-eclipse-plugin
Length of output: 4280
🏁 Script executed:
Repository: espressif/idf-eclipse-plugin
Length of output: 54
🌐 Web query:
Eclipse LSP4E LanguageServiceAccessor API compatibility 0.30.0💡 Result:
The Eclipse LSP4E LanguageServiceAccessor API is compatible with version 0.30.0. No breaking changes affecting this API are documented in the 0.30.0 release notes. The release includes adaptation to LSP4J 1.0.0 (which has breaking changes like removed deprecated APIs) and removal of some deprecated APIs in LSP4E via PR
#1496, but LanguageServiceAccessor is not mentioned as affected. Access to language servers remains available through classes like LanguageServersRegistry and LanguageServers, as shown in source code snippets. Official documentation and changelogs confirm no explicit incompatibility for this API.Citations:
🌐 Web query:
Eclipse LSP4E LanguageServerWrapper serverDefinition property 0.30.0 breaking changes💡 Result:
In Eclipse LSP4E version 0.30.0 (released February 11, 2026), the primary breaking change listed in the official release notes is "refactor: Get rid of some deprecated APIs by
@FlorianKroissin#1496". This PR removes usages of deprecated APIs, likely from the newly adopted LSP4J 1.0.0 (feat: Adapt LSP4E to LSP4J vers. 1.0.0 by@travkin79in#1421), which itself removed several deprecated constructors, static methods, and other APIs. No sources explicitly detail changes to the LanguageServerWrapper.serverDefinition property itself. The property remains public final in LanguageServerWrapper as per available code snippets. Any breaking changes would stem indirectly from LSP4J adaptations or deprecated Eclipse Platform APIs removed in the refactor, potentially affecting custom LanguageServerDefinition implementations if they relied on now-removed deprecated methods. Other changes in 0.30.0 are mostly fixes and features (e.g., SVG icons, JUnit updates, markdown parser singleton), with no other breaking changes noted.Citations:
🏁 Script executed:
Repository: espressif/idf-eclipse-plugin
Length of output: 487
🌐 Web query:
Eclipse LSP4J 1.0.0 breaking changes deprecated APIs removal💡 Result:
Eclipse LSP4J 1.0.0, released February 2026, includes several breaking API changes focused on removing long-deprecated elements and updating to new LSP/DAP specifications. Key breaking changes: - Removed deprecated org.eclipse.lsp4j.websocket bundle. Migrate to org.eclipse.lsp4j.websocket.jakarta or stay on LSP4J 0.x. - Removed deprecated ConcurrentMessageProcessor.startProcessing; use beginProcessing instead (
#922). - Removed@Deprecatedannotations from members deprecated in LSP/DAP protocols (#895). - Removed various deprecated APIs via issues#874,#875,#876,#877,#880: -#874: General deprecated API removal. -#875: Deprecated convenience constructors in protocol files. -#876: Deprecated LanguageServerAPI annotation (use JsonRpcData). -#877: Deprecated static methods in Either class (use TypeUtils). -#880: Deprecated get/set properties in FormattingOptions. - Type change: TextDocumentEdit.edits from List to List<Either<TextEdit, SnippetTextEdit>>. - Implemented LSP 3.18.0 (beta) and DAP 1.70.0, potentially introducing new structures. Full details in official CHANGELOG.md and japicmp report at https://download.eclipse.org/lsp4j/updates/releases/1.0.0/japicmp-report/. Projects like Spring Tools note API changes requiring updates when migrating to 1.0.0.Citations:
1.0.0spring-projects/spring-tools#1781Update MANIFEST.MF bundle version constraint to match LSP4E target version.
The
org.eclipse.lsp4ebundle version inbundles/com.espressif.idf.core/META-INF/MANIFEST.MFis pinned to0.18.18, which is severely outdated and inconsistent with the LSP4E 0.30.0 target being updated. The constraint should be updated to0.30.0to reflect the actual compatibility requirement.The code in
LspService.javauses internal LSP4E APIs (LanguageServiceAccessor.getStartedWrappers(),LanguageServerWrapper.serverDefinition.id,execute(),restart()) marked with@SuppressWarnings("restriction"). These specific APIs are compatible with LSP4E 0.30.0, but keeping the bundle constraint aligned with the target version ensures consistency and clarity about supported versions.🤖 Prompt for AI Agents