members of a deprecated type are not implicitly deprecated

[HannesWell]

Currently the eclipse.platform.releng.aggregator master build (and I expect also the next I-build) fails with the following compilation error:

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:5.0.1-SNAPSHOT:compile (default-compile) on project org.eclipse.jdt.debug: Compilation failure: Compilation failure: 
[ERROR] /home/jenkins/agent/workspace/atform.releng.aggregator_PR-3432/eclipse.jdt.debug/org.eclipse.jdt.debug/model/org/eclipse/jdt/internal/debug/core/model/JDIStackFrame.java:[1574] 
[ERROR] 	@SuppressWarnings("deprecation")
[ERROR] 	                  ^^^^^^^^^^^^^
[ERROR] Unnecessary @SuppressWarnings("deprecation")

As the code didn't change for quite some time, I assume it's actually a bug in the compiler, that the deprecated method called within it, is not detected:
https://github.com/eclipse-jdt/eclipse.jdt.debug/blob/d0cd55117a2260b7cdd3f71210befbde9786b055/org.eclipse.jdt.debug/model/org/eclipse/jdt/internal/debug/core/model/JDIStackFrame.java#L1574-L1578

With the latest I-build from this afternoon, I20251025-0900, it was still working.

[laeubi]

Maybe a side-effect of

• Do not emit restriction warning on inherited method #4293

but deprecation should not be touched here?!?

[laeubi]

If I remove that in the IDE updated to latest ibuild I still get an error that the suppress is required.

[iloveeclipse]

Maybe a side-effect of

• Do not emit restriction warning on inherited method #4293

but deprecation should not be touched here?!?

This is a regression from 545483d / #4293.

Considering how much discussion was done to merge #4293 I don't expect the fix to be fast, so ideally we simply revert 545483d to unblock SDK build.

[laeubi]

I'm working on a fix right now ...

[iloveeclipse]

I'm working on a fix right now ...

I would prefer to wait for @stephan-herrmann assesment on whole topic and simply revert the last commit till then. The original fix isn't anything urgent that is "must have", having SDK build running is urgent.

[laeubi]

SDK build running is urgent.

We currently have the problem that tests don't start and waiting for the 10h timeout for further analysis... so what specifically urgent we are looking for?