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

Use https for repo.gradle.org #154

Merged
merged 1 commit into from
Apr 6, 2020

Conversation

mkmaier
Copy link
Contributor

@mkmaier mkmaier commented Jan 8, 2020

This fixes downloading of gradle resources, since gradle.org does not allow http anymore

@uschindler
Copy link
Member

Hi,
the reason for using HTTP was mainly that forbiddenapis is still built with Java 6. If the Gradle server is one of those that no longer allows TLS 1.0/1.1 we have the problem that it can't be built anyways.
Nevertheless I am looking into that. It's too bad that Gradle is not on Maven Central.

@uschindler uschindler self-assigned this Jan 8, 2020
@uschindler uschindler added the bug label Jan 8, 2020
@uschindler uschindler added this to the 2.8 milestone Jan 8, 2020
@uschindler
Copy link
Member

That's also the reason why there's "ivy.maven-central.backup", which is set by ANT based on Java version.

@mkmaier
Copy link
Contributor Author

mkmaier commented Jan 9, 2020

Maybe this would be a good time to drop support for java 6. The current version will still be available, so if there are really users still on java 6, they can just use that.

Note: This PR is only a preparation for what I really want to do, which is adding configuration for the gradle build cache to work properly. This would also mean requiring at least gradle 3.2, which introduces @Classpath.

@uschindler uschindler merged commit 883d03f into policeman-tools:master Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

3 participants