This message was deleted.
# community-supports
Slackbot
09/27/2023, 7:19 AMThis message was deleted.
v
Vladimir Orany
09/27/2023, 7:22 AMthe other difference is that the failing build has extra
runtimeClasspathv
Vampire
09/27/2023, 8:11 AMMaybe you did not wire things together properly and it just accidentally works locally because the producer task is run first, or because the jar is still on disk but stale. Hard to say without having the build at hand.
v
Vladimir Orany
09/27/2023, 8:12 AMfor some unknown reason it started to fail on a branch that switched from using internal BOM to using an internal version catalog. it works locally even in a fresh cloned project đ
Vladimir Orany
09/27/2023, 8:13 AMand all the wiring is still working properly on the main branch
Vladimir Orany
09/27/2023, 8:20 AMand the
jargroovyCompileVladimir Orany
09/27/2023, 8:24 AMbut to give more context, there are more builds on this branch failing (again only on CI) because of this dependent library
Vladimir Orany
09/27/2023, 8:28 AMbut neither the failing nor the dependent task does not come from the cache so it does not like like a caching issue
Vladimir Orany
09/27/2023, 8:45 AMand I have just tried to use default Ubuntu runner instead of our custom one and got the same result
Vladimir Orany
09/27/2023, 3:14 PMFYI I wasnât able to solve the issue. I have found only a workaround - extracting some parts from the failing library and rewritten the code into Java. with this update, I was able to make it working again
2 Views