Remove HikariCP shading and expose as transitive dependency#111
Merged
Remove HikariCP shading and expose as transitive dependency#111
Conversation
Co-authored-by: garricko <1234201+garricko@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove shading of Hikari to expose as dependency
Remove HikariCP shading and expose as transitive dependency
Mar 10, 2026
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.
HikariCP was being bundled into the shaded JAR with a relocated package, hiding it from consumers and requiring them to declare it separately if needed directly.
Changes
artifactSet— no longer bundled/relocated into the output JARcom.zaxxer.hikari→shaded.com.github.susom.database.shaded.com.zaxxer.hikarirewrite<optional>true</optional>from the HikariCP dependency — consumers now receive HikariCP as a standard transitive dependency via Maven dependency resolutionWarning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
us-west1-maven.pkg.dev/usr/lib/jvm/temurin-17-jdk-amd64/bin/java /usr/lib/jvm/temurin-17-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -classpath /usr/share/apache-maven-3.9.12/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.12/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.12 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.12/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/database/database org.codehaus.plexus.classworlds.launcher.Launcher clean package -Phsqldb -Duser.timezone=America/Los_Angeles -Dhsqldb.database.url=jdbc:hsqldb:file:target/hsqldb;shutdown=true -Dhsqldb.database.user=SA -Dhsqldb.database.password=(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.