This message was deleted.
# community-support
s
This message was deleted.
v
As you see in the "following locations" list, it searched in
mavenLocal()
(which you really should strongly consider to never use, especially not as first repository and especially not without content filter, as it is broken by design and makes builds slower and flaky) and in
google()
but neither of these repositories has this dependency. So you probably miss to define
mavenCentral()
as repository.
j
Indeed I found a
mavenLocal
in
:module
! It’s weird it worked before (I’m migrating the dependencies to a version catalog)
v
Did I mention
mavenLocal
makes your build flaky as it is broken by design (in Maven already)?
If you happen to have built some Maven project before which caused that Jackson dependency be present in
mavenLocal()
, your build succeeds as the dependency is found. If then somehow the entry in
mavenLocal()
vanishes, the build stops working as it is no longer found.
j
We do have a CI/CD process that should start from scratch and download fresh dependencies everytime, so I have no idea how this manage to work before. The project is pretty old (2014) and some gradle files have accumulated a metric tone of trash. You’ll probably hear from me again soon while I try to clean up the mess hehe
👌 1
v
Here you can read about some of the major shenenigans with `mavenLocal()`: https://docs.gradle.org/current/userguide/declaring_repositories.html#sec:case-for-maven-local