Skip to content

still using jcenter #4095

@chris-brace

Description

@chris-brace

Nearly one year ago gradle and others issued guidance to stop using jcenter(). https://blog.gradle.org/jcenter-shutdown This plugin is still there and is now breaking CI because it cant be retrieved

A problem occurred configuring project ':backend:oas3-annotationprocessor:demo'.
> Could not resolve all artifacts for configuration ':backend:oas3-annotationprocessor:demo:classpath'.
   > Could not resolve io.swagger.core.v3:swagger-gradle-plugin:2.1.12.
     Required by:
         project :backend:oas3-annotationprocessor:demo > io.swagger.core.v3.swagger-gradle-plugin:io.swagger.core.v3.swagger-gradle-plugin.gradle.plugin:2.1.12
      > Could not resolve io.swagger.core.v3:swagger-gradle-plugin:2.1.12.
         > Could not get resource 'https://plugins.gradle.org/m2/io/swagger/core/v3/swagger-gradle-plugin/2.1.12/swagger-gradle-plugin-2.1.12.module'.
            > Could not GET 'https://jcenter.bintray.com/io/swagger/core/v3/swagger-gradle-plugin/2.1.12/swagger-gradle-plugin-2.1.12.module'. Received status code 502 from server: Bad Gateway

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions