Created by: sebastien-rosset
Trying to eliminate the use of http as much as possible. Some of these changes are documentation only and do not affect the build but we should use https nonetheless. There are multiple use of http://central.maven.org, but that site returns error 403 with a message stating to use http://repo1.maven.org. I've replaced these.
There are some http URL that don't exist anymore. I'm not sure what to do about it, and it's not clear they are used anyway.
I did a cursory search to find use of http://:
grep -r 'http://' . | grep -v xmlns |grep -v schemaLocation | wcRight now it yields over 6000 results. Unfortunately we can't do a simple search and replace.
Slightly better way to find references to http://
grep -r 'http://' . | grep -v xmlns |grep -v schemaLocation | sed -rn 's/.*(http:\/\/[^ )"]+).*/\1/p' | sort | uniqIt yields 779 results.
./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).master, 4.3.x, 5.0.x. Default: master.
To run a merge request pipeline, the jobs in the CI/CD configuration file must be configured to run in merge request pipelines.