Skip to content

fix: Suppress JVM warnings from Lucene within CLI - #8003

Merged
jeremylong merged 1 commit into
dependency-check:mainfrom
chadlwilson:fix-jvm-warning-logs
Oct 6, 2025
Merged

jeremylong merged 1 commit into
dependency-check:mainfrom
chadlwilson:fix-jvm-warning-logs

Conversation

@chadlwilson

@chadlwilson chadlwilson commented Oct 4, 2025 •

Copy link
Copy Markdown
Collaborator

Description of Change

Follow-up to #7979 to remove remaining JVM warnings from the normal log output on JDK 21/25 CLI/Docker usage.

Alternate is to consider the use of all of these native Lucene features and whether it is worthwhile given the
scale of ODC's Lucene usage. (e.g the vector API probably isn't accessible/usable right now in some configurations)

Related issues

Have test cases been added to cover the new functionality?

no

@boring-cyborg boring-cyborg Bot added the cli changes to the cli label Oct 4, 2025
@chadlwilson
chadlwilson force-pushed the fix-jvm-warning-logs branch from c2707ae to ecbee4b Compare October 4, 2025 05:04
@chadlwilson chadlwilson changed the title fix: Suppress JVM warnings from Lucene within CLI feat: Suppress JVM warnings from Lucene within CLI Oct 4, 2025
Signed-off-by: Chad Wilson <29788154+chadlwilson@users.noreply.github.com>
@jeremylong jeremylong changed the title feat: Suppress JVM warnings from Lucene within CLI fix: Suppress JVM warnings from Lucene within CLI Oct 6, 2025
@jeremylong jeremylong added this to the 12.1.7 milestone Oct 6, 2025
@jeremylong
jeremylong merged commit ae97b08 into dependency-check:main Oct 6, 2025
7 checks passed
@chadlwilson
chadlwilson deleted the fix-jvm-warning-logs branch October 6, 2025 14:30
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Nov 6, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cli changes to the cli

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WARNINGs when executing analysis with Java 21

2 participants