Eclipse 2026-03 compatibility #73#76
Merged
aclement merged 3 commits intoeclipse-aspectj:masterfrom Feb 11, 2026
Merged
Conversation
basilevs
changed the title
Contributor
Author
|
@aclement PTAL |
Contributor
Author
|
The workflow somehow runs without approval. Nice. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #73
This fixes incompatibility with modern JDT IDE (we fixed compatibility with modern Eclipse runtime in #70)
Potential issues:
AJSourceElementParser2.consumeFormalParameter()is replaced on a guessASTResolving.getPossibleTypeKinds()boolean parameterIn general, I've tried to concentrate non-trivial fixes in the second commit
Requires a new deployment job that uses the new Maven profile (
-P e439instead of the old-P e431)