Remove now unnecessary API-tools tags in JNIBridge #578
Conversation
This file contains 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
HannesWell
changed the title
Because JNIBridge is now a package-private class it cannot be referenced from other bundles anyway. So there is no need for API-tags that prohibit it. Follow-up of eclipse-equinox#565
HannesWell
force-pushed
the
remove-api-tags
branch
from
579ea81
to
f451125
Compare
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.
Because JNIBridge is a package-private class since #565 it cannot be referenced from external bundles anyway. So there is no need for API-tags to prohibit that.