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
HikariCP 4 fails to be resolved in Gradle #1725
Closed
zml2008 opened this issue
Jan 24, 2021
· 3 comments
· Fixed by octawizard/padles-api#32, enonic/lib-sql#28, navikt/fplos#871 or navikt/fptilbake#1253
Closed
HikariCP 4 fails to be resolved in Gradle #1725
zml2008 opened this issue
Jan 24, 2021
· 3 comments
· Fixed by octawizard/padles-api#32, enonic/lib-sql#28, navikt/fplos#871 or navikt/fptilbake#1253
Comments
Hi, This is happening too when pulling in the updated dependency with Switching to HikariCP
Reverting back to HikariCP |
@dharrigan @zml2008 Fix coming momentarily. |
Fixed, release publishing in ~30min. |
This was referenced Mar 4, 2021
Closed
This was referenced Mar 17, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems like HikariCP 4 is not properly resolved due to a missing
slf4j.version
property.This has come up from a renovate PR bumping the HikariCP version to 4.0.0.
The relevant line in the build log is (GH Actions log link):
This might be a limitation due to Gradle's pom resolution not supporting some of the more niche features of Maven's artifact descriptor (since it appears the
slf4j.version
property is defined only in profiles in the pom) -- unfortunately I don't have any maven projects left to test in.The text was updated successfully, but these errors were encountered: