Hi Anna,
That's a strange problem, earlier this week we fixed the bazel build starting from branch stable-5.13 and
merged that up to master. While doing that I ran both the bazel build and the maven build for each of the
branches and they succeeded.
Since Tuesday all builds on branch stable-6.4 or newer fail with strange classpath issues.
I ran git bisect between stable-6.3 and master and found that jgit commit b398bb91ab28b799ea39dc2d1b5bd0b849392443
to fail the build if any dependency isn't yet license-approved by Eclipse. This commit was introduced on branch stable-6.4
and submitted on Oct 15, 2022. This worked for 6 months and started failing this Tuesday. I think the problem is that we
depend on the 0.0.1-SNAPSHOT version of the plugin since it didn't yet publish a release. This means we depend on the
latest build published for this plugin which can change any time.
2 commits were merged for the plugin on Apr 24
I guess one of them is the culprit.
I conclude that the dash license-tool-plugin recently introduced a change breaking the jgit builds.
Reverting the commit b398bb91ab28b799ea39dc2d1b5bd0b849392443 fixes the problem for the jgit build.
I will try to build the dash license-tool-plugin locally and bisect its history to identify the change that broke the jgit build.