Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

still using jcenter #4095

Closed
chris-brace opened this issue Jan 12, 2022 · 7 comments
Closed

still using jcenter #4095

chris-brace opened this issue Jan 12, 2022 · 7 comments
Assignees

Comments

@chris-brace
Copy link

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
@natebranchapp
Copy link

Came here to same we are experiencing the same issue.

@chris-brace
Copy link
Author

one thing of note, it appears that https://plugins.gradle.org/m2/io/swagger/core/v3/swagger-gradle-plugin/2.1.12/swagger-gradle-plugin-2.1.12.module is redirecting to jcenter. i guess it's possible that this is an issue with the plugin portal but its difficult for me to tell. especially since the rest of our plugins are working fine.

@mtyeh411
Copy link

@chris-brace
Copy link
Author

this needs to be removed, no? not sure what else tbh https://github.com/swagger-api/swagger-core/blob/v2.1.12/modules/swagger-gradle-plugin/build.gradle#L18

yeah i cant tell what causes the plugin to be in jcenter or if that line you linked to determines what gradles plugin publisher does

@chris-brace
Copy link
Author

chris-brace commented Jan 12, 2022

The mirror redirect appears to be a gradle issue https://status.gradle.com

I fixed this for the mean time by building the gradle plugin on my own and publishing it to a private maven repo we host on s3.

Im going to leave this open because the jcenter() line in this build.gradle needs to be removed.

For reference, i mentioned this issue on gradles forum too https://discuss.gradle.org/t/plugins-redirecting-to-jcenter/41909/6

@frantuma frantuma self-assigned this Jan 13, 2022
@Akaame
Copy link

Akaame commented Jan 19, 2022

Any updates on this issue?

@frantuma
Copy link
Member

frantuma commented Jan 24, 2022

Thanks all for reporting this.

I am not sure about the cause of the issues with plugin resolution from plugin portal "redirecting" to jcenter (as from some tests I am not experiencing issues in plugin 2.1.12 resolution atm), however jcenter() references have been removed in #4099.

Closing ticket, please reopen/comment if you're still experiencing issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants