Skip to content

Get rid of BND warnings#1933

Merged
cstamas merged 1 commit into
apache:masterfrom
cstamas:bnd-warnings
Jun 24, 2026
Merged

Get rid of BND warnings#1933
cstamas merged 1 commit into
apache:masterfrom
cstamas:bnd-warnings

Conversation

@cstamas

@cstamas cstamas commented Jun 24, 2026

Copy link
Copy Markdown
Member

By properly formatting bnd parameters (follow emitted advice, add trailing :).


FTR, warning was:

[INFO] --- bnd:7.3.0:bnd-process (bnd-process) @ maven-resolver-spi ---
[WARNING] /home/cstamas/Worx/apache-maven/RELEASE/maven-resolver/maven-resolver-spi/pom.xml [18:74]: No value specified for key: -jpms-module-info. An empty value should be specified as '-jpms-module-info:' or '-jpms-module-info=': <<              -jpms-module-info
      -removeheaders Automatic-Module-Name>>

And properly format bnd parameters.
@cstamas cstamas added this to the 2.0.19 milestone Jun 24, 2026
@cstamas cstamas self-assigned this Jun 24, 2026
@cstamas cstamas marked this pull request as ready for review June 24, 2026 09:48

@gnodet gnodet left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@cstamas cstamas merged commit 331895b into apache:master Jun 24, 2026
14 checks passed
@cstamas cstamas deleted the bnd-warnings branch June 24, 2026 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants