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

Move from Maven Central/Sonatype to jCenter (or other repo that uses HTTPS) #494

Closed
robfletcher opened this issue Aug 30, 2015 · 4 comments

Comments

@robfletcher
Copy link
Contributor

Originally reported on Google Code with ID 372

For security reasons, usage of Maven Central should be deprecated.

See:
http://blog.ontoillogical.com/blog/2014/07/28/how-to-take-over-any-java-developer/

Reported by msgilligan on 2014-07-29 10:37:48

@robfletcher
Copy link
Contributor Author

AFAIK, jCenter proxies Maven Central. Resolving Spock from jCenter works fine for me.

Reported by pniederw on 2014-07-29 14:06:02

@leonard84
Copy link
Member

Use JCenter it provides https

@szpak
Copy link
Member

szpak commented Nov 7, 2015

@robfletcher Isn't it an obsolete case? Maven Central provides HTTPS access as well - https://repo1.maven.org/maven2/org/spockframework/spock-core/1.0-groovy-2.4/.

What's more it has seemed to be active since August 2014 - http://www.infoq.com/news/2014/08/Maven-SSL-Default

@szpak
Copy link
Member

szpak commented Nov 7, 2015

Ups, I missed it was an issue imported from Google Code and it's date is not August 2015, but "2014-07-29 10:37:48".

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

No branches or pull requests

3 participants