Fix deprecation warning suppression for inherited interface methods#12
Draft
Fix deprecation warning suppression for inherited interface methods#12
Conversation
…cated method Co-authored-by: laeubi <1331477+laeubi@users.noreply.github.com>
… deprecation warnings Co-authored-by: laeubi <1331477+laeubi@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add testcase for deprecated method regression
Fix deprecation warning suppression for inherited interface methods
Oct 26, 2025
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
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 regression from PR eclipse-jdt#4293 where deprecation warnings were incorrectly suppressed when calling deprecated methods through inherited interfaces, causing
@SuppressWarnings("deprecation")to be flagged as unnecessary.Problem
Root Cause
ASTNode.isMethodUseDeprecated()incorrectly reused theisExplicitUseflag (introduced for access restriction checking) to suppress deprecation warnings for non-directly-declared method calls.Changes
ASTNode.isMethodUseDeprecated()that suppressed deprecation warnings when!isExplicitUse && !@DeprecatedtestInheritedInterfaceDeprecatedMethod()andtestInheritedInterfaceDeprecatedMethodWithSuppressWarnings()to verify correct behaviorDeprecation warnings now emit for all deprecated methods regardless of inheritance hierarchy. Access restriction behavior remains unchanged (correctly checks only explicit uses).
Addresses TODO comment: "consider separating concerns between deprecation and access restriction"
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
repo.eclipse.org/usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/eclipse.jdt.core/eclipse.jdt.core org.codehaus.plexus.classworlds.launcher.Launcher clean compile -pl org.eclipse.jdt.core.compiler.batch,org.eclipse.jdt.core.tests.compiler -am -DskipTests(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.