Skip to content

Conversation

@trancexpress
Copy link
Contributor

Fixes: #2600

@trancexpress
Copy link
Contributor Author

trancexpress commented Nov 3, 2025

With this change I see warnings in the IDE...:

Description	Resource	Path	Location	Type
StandardJavaElementContentProvider implements non-API interface IWorkingCopyProvider	StandardJavaElementContentProvider.java	/org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui	line 74	API Usage Problem
Description	Resource	Path	Location	Type
ImportReferencesCollector extends non-API type GenericVisitor	ImportReferencesCollector.java	/org.eclipse.jdt.core.manipulation/common/org/eclipse/jdt/core/manipulation	line 75	API Usage Problem

Any idea if the check is broken @iloveeclipse ?

https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/2535/checks?check_run_id=54347069909

@trancexpress
Copy link
Contributor Author

OK, using latest I-build (02.11), I don't see the warnings. Must be something that was improved in PDE.

@jjohnstn jjohnstn merged commit 82a682e into eclipse-jdt:master Nov 4, 2025
13 checks passed
@trancexpress
Copy link
Contributor Author

Thank you for merging @jjohnstn !

iloveeclipse added a commit to iloveeclipse/eclipse.jdt.ui that referenced this pull request Nov 7, 2025
This reverts commit 82a682e as it was
based on wrong assumptions / bug in API tooling.

Fixes eclipse-jdt#2600
iloveeclipse added a commit that referenced this pull request Nov 7, 2025
This reverts commit 82a682e as it was
based on wrong assumptions / bug in API tooling.

Fixes #2600
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unused API filter errors in builds

2 participants