[c-dilks]

Using several repositories causes each of them to 404 often, since Maven will check each one of them for each dependency, when only one of the repositories actually has that dependency. This can lead to 429 errors, e.g.,

  > Could not resolve javax.annotation:javax.annotation-api:1.3.2.
     Required by:
         root project 'clara-java'
      > Could not resolve javax.annotation:javax.annotation-api:1.3.2.
         > Could not parse POM https://repo.maven.apache.org/maven2/javax/annotation/javax.annotation-api/1.3.2/javax.annotation-api-1.3.2.pom
            > Could not resolve net.java:jvnet-parent:3.
               > Could not resolve net.java:jvnet-parent:3.
                  > Could not get resource 'https://code.jlab.org/api/v4/projects/959/packages/maven/net/java/jvnet-parent/3/jvnet-parent-3.pom'.
                     > Could not HEAD 'https://code.jlab.org/api/v4/projects/959/packages/maven/net/java/jvnet-parent/3/jvnet-parent-3.pom'.
                        > Received status code 429 from server: Too Many Requests

Instead, we can use a GitLab group-level repository, which we know has most of the dependencies.

The real solution would be a repository manager in front of GitLab, such as Nexus or Artifactory; I think there's a GitLab repository manager too, but likely not available on our tier.