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 URL to download dependencies #2248

Merged
merged 2 commits into from
Feb 27, 2019
Merged

Use https URL to download dependencies #2248

merged 2 commits into from
Feb 27, 2019

Conversation

wing328
Copy link
Member

@wing328 wing328 commented Feb 27, 2019

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh, ./bin/security/{LANG}-petstore.sh and ./bin/openapi3/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
  • Filed the PR against the correct branch: master, 3.4.x, 4.0.x. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

  • Use https instead of http URL to download dependencies
  • fix Groovy default value in the template

cc
Kotlin tech committee: @jimschubert (2017/09), @dr4ke616 (2018/08)
Scala tech committee: @clasnake (2017/07), @jimschubert (2017/09), @shijinkui (2018/01), @ramzimaalej (2018/03)

mavenCentral(artifactUrls: ['http://maven.springframework.org/milestone'])
maven { url "http://$artifactory:8080/artifactory/repo" }
mavenCentral(artifactUrls: ['https://maven.springframework.org/milestone'])
maven { url "https://$artifactory:8080/artifactory/repo" }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This repository is only ever going to work in very specific user environments. Is there any value in keeping it? If it's for internal corporate artifact servers, some of them are only available over HTTP (because they are only available in a companies intra-net).

I suggest either removing it or making it so that the protocol http vs https is configurable by the user.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any value in keeping it?

I do not have an answer but I agree with you to remove these entries and only add back when there's a valid use case or reason.

@@ -19,8 +18,6 @@ buildscript {
repositories {
mavenCentral()
mavenLocal()
mavenCentral(artifactUrls: ['https://maven.springframework.org/milestone'])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might need this, I don't know.

@@ -19,8 +18,6 @@ buildscript {
repositories {
mavenCentral()
mavenLocal()
mavenCentral(artifactUrls: ['https://maven.springframework.org/milestone'])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might need this, I don't know.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The project compiles without issue. If anyone needs this for whatever reasons, we can certainly add it back.

Copy link
Contributor

@JLLeitschuh JLLeitschuh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Nice work @wing328!

@wing328
Copy link
Member Author

wing328 commented Feb 27, 2019

@JLLeitschuh thanks for the quick review. I'll merge this PR into master once the CI tests pass

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

Successfully merging this pull request may close these issues.

2 participants