Tags
Creators
Details
3.53.0.0+2026-04-14
Compatibility
Changes
modrinth body: holder is functionally inert when bundled driver exists
Tested empirically (paper-1.12.2 with engine 3.21.0 bundled, paper-1.21.11 with engine 3.49.1.0 in libraries/) — the bundled driver wins driver-class resolution every time, regardless of whether the holder is installed. Plugin classloaders delegate to the server parent classloader first; parent already holds org.sqlite.JDBC / com.mysql.cj.jdbc.Driver; holder's PluginClassLoader is never consulted; DriverManager only ever has the bundled driver registered.
Body now states this directly so operators don't install the mod expecting it to upgrade their bundled driver. Holder remains useful on Fabric/NeoForge (no bundled) and Bukkit forks that strip the driver.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:bTTf2DEw:GcD6Hzn7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bTTf2DEw:GcD6Hzn7"
}

