Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning: Explicitly loaded driver org.h2.Driver from classpath #7118

Closed
OrangeDog opened this issue Oct 30, 2024 · 4 comments · Fixed by #7155
Closed

Warning: Explicitly loaded driver org.h2.Driver from classpath #7118

OrangeDog opened this issue Oct 30, 2024 · 4 comments · Fixed by #7155
Labels

Comments

@OrangeDog
Copy link
Contributor

OrangeDog commented Oct 30, 2024

Describe the bug

[INFO] --- dependency-check:11.1.0:check (default-cli) @ demo ---
[WARNING] Explicitly loaded driver org.h2.Driver from classpath; if JDBCv4 service loading is supported by the driver you should remove the dbDriver configuration

Message is also duplicated to stderr.

Version of dependency-check used
Maven plugin 11.1.0

To Reproduce
Steps to reproduce the behavior:

  1. mvn dependency-check:check

Expected behavior
No warnings

Additional context
Related to #7115?

@OrangeDog OrangeDog added the bug label Oct 30, 2024
@OrangeDog OrangeDog changed the title Warning; Explicitly loaded driver org.h2.Driver from classpath Warning: Explicitly loaded driver org.h2.Driver from classpath Oct 30, 2024
@jeremylong
Copy link
Owner

Understand the warning - but for reasons we've had to revert to legacy driver loading mechanisms.

@aikebah
Copy link
Collaborator

aikebah commented Oct 30, 2024

@jeremylong I think for the same reason we should remove this warning, which was introduced to signal uses of the explicit drivername triggering the 'legacy way' of driver registration where not required (assuming that JDBC 4 SPI driver loading would work flawlessly, which has been proven to be a wrong assumption.

https://github.com/jeremylong/DependencyCheck/pull/6938/files#diff-1bd6d053c4d3e4fd27267ae889d2f7b7fa257855e928959564295c1736e815d1

@jeremylong
Copy link
Owner

Thank you @aikebah - I completely missed that I had written this log message. fixing this shortly.

@aikebah
Copy link
Collaborator

aikebah commented Nov 13, 2024

Thank you @aikebah - I completely missed that I had written this log message. fixing this shortly.

That's because you didn't... I wrote it, you only merged it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants