Gemnasium fails with unresolved dependencies (gemnasium-maven)

Since the release of the following MR: gitlab-org/security-products/analyzers/gemnasium!790 (merged), Gemnasium fails for our projects with unresolved dependencies. These projects however worked perfectly fine on Gemnasium prior to the htmlDependencyReport change, and we don't see any reason why dependencies like org.hibernate.reactive:hibernate-reactive-core:2.3.1.Final, as they are available on Maven central. Furthermore, all our compile and test stages have no issues finding these dependencies.

Here are some example projects with failing dependency lookups for Gemnasium:

Apologies if this is something on our end that is getting caught now by a stricter Gemnasium, but we have looked at this and we really don't see how these projects should not work perfectly fine on Gemnasium, especially because they all worked before the htmlDependencyReport change so the old behaviour that this MR pointed back to should have still worked on these projects.

I think @candrews and @hacks4oats are most relevant for this issue?

Workaround

The current workaround is to pin to an earlier version of Dependency Scanning (v5.2.16).

include:
  - template: Security/Dependency-Scanning.gitlab-ci.yml

gemnasium-maven-dependency_scanning:
  image: "registry.gitlab.com/security-products/gemnasium-maven:5.2.16"
Edited by Philip Cunningham