Skip to content
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

deprecation markers with since > BREE are not shown in Problems view but in Editor #2873

Closed
jukzi opened this issue Aug 22, 2024 · 2 comments · Fixed by #2874
Closed

deprecation markers with since > BREE are not shown in Problems view but in Editor #2873

jukzi opened this issue Aug 22, 2024 · 2 comments · Fixed by #2874
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jukzi
Copy link
Contributor

jukzi commented Aug 22, 2024

example: org.eclipse.e4.ui.css.swt.helpers.CSSSWTImageHelper shows a warning
The constructor URL(String) is deprecated since version 20 in the editor but not in the Problems View.
Even if i configure the warning to be an error it is not shown in the Problems view while compile warings/errors of other type in the same file are shown.
image
The project is configured to have 17 compliance. When i change the the compliance level to 21 then both editor and problem view are consistently showning the marker.
image

I expect the warning in the editor to match the warnings in the problems view, no matter which compliance level i selected - shouldn't i?

@jukzi jukzi added the bug Something isn't working label Aug 22, 2024
@jukzi jukzi changed the title deprecation markers with since < BREE are not shown in Problems view but in Editor deprecation markers with since > BREE are not shown in Problems view but in Editor Aug 22, 2024
@jjohnstn jjohnstn transferred this issue from eclipse-jdt/eclipse.jdt.ui Aug 29, 2024
@jjohnstn jjohnstn self-assigned this Aug 29, 2024
@jjohnstn
Copy link
Contributor

I have a fix for this in jdt.core.

jjohnstn added a commit to jjohnstn/eclipse.jdt.core-1 that referenced this issue Aug 29, 2024
@jjohnstn jjohnstn added this to the 4.34 M1 milestone Sep 4, 2024
jjohnstn added a commit to jjohnstn/eclipse.jdt.core-1 that referenced this issue Sep 5, 2024
jjohnstn added a commit to jjohnstn/eclipse.jdt.core-1 that referenced this issue Sep 20, 2024
jjohnstn added a commit to jjohnstn/eclipse.jdt.core-1 that referenced this issue Sep 26, 2024
jjohnstn added a commit to jjohnstn/eclipse.jdt.core-1 that referenced this issue Oct 8, 2024
jjohnstn added a commit to jjohnstn/eclipse.jdt.core-1 that referenced this issue Oct 17, 2024
jjohnstn added a commit to jjohnstn/eclipse.jdt.core-1 that referenced this issue Oct 24, 2024
jjohnstn added a commit to jjohnstn/eclipse.jdt.core-1 that referenced this issue Oct 25, 2024
@stephan-herrmann
Copy link
Contributor

I've filed #3168 for the core problem, but as mentioned there, I don't know if solving that one is actually worth the effort ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants