Get rid of BND warnings#1933
Merged
Merged
Conversation
And properly format bnd parameters.
gnodet
approved these changes
Jun 24, 2026
gnodet
left a comment
Contributor
There was a problem hiding this comment.
Clean and correct fix. The three affected modules are the only ones using BND instruction syntax without the required colon separator — the other modules with bnd.instructions.additions use standard OSGi manifest headers that already include colons.
LGTM.
Fully automatic review from Claude Code
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.
By properly formatting bnd parameters (follow emitted advice, add trailing
:).FTR, warning was: