7903936: Update variable names in build.sh documentation

[asilichenko]

Changed variable name CURL_OPTS to CURL_OPTIONS in the documentation block "Some noteworthy control variables" in build.sh.

CURL_OPTIONS is used in the download_using_curl() function in build-support/build-common.sh.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• CODETOOLS-7903936: Update variable names in build.sh documentation (Bug - P4)

Reviewers

• Christian Stein (@sormuras - Committer)
• Iris Clark (@irisclark - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jtreg.git pull/238/head:pull/238
$ git checkout pull/238

Update a local copy of the PR:
$ git checkout pull/238
$ git pull https://git.openjdk.org/jtreg.git pull/238/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 238

View PR using the GUI difftool:
$ git pr show -t 238

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jtreg/pull/238.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

Hi @asilichenko, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user asilichenko" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

[openjdk]

@asilichenko This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

7903936: Update variable names in build.sh documentation

Reviewed-by: cstein, iris

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@sormuras, @irisclark) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[asilichenko]

/signed

[bridgekeeper]

Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

[asilichenko]

/signed

[bridgekeeper]

Already processed the signed command

[sormuras]

Thanks for the contribution @asilichenko!

• Please update this pull request to also include the changes from Rename WGET_OPTS to WGET_OPTIONS in build.sh #239 and close Rename WGET_OPTS to WGET_OPTIONS in build.sh #239 in favor of this pull request.
• Please update the title of this pull request to read: 7903936: Update variable names in build.sh documentation , I created https://bugs.openjdk.org/browse/CODETOOLS-7903936 for this renaming task.
• Please update the second year in line 4 of build.sh from 2024 to 2025.

[mlbridge]

Webrevs

• 03: Full - Incremental (26d19213)
• 02: Full - Incremental (a1c638f9)
• 01: Full - Incremental (14692275)
• 00: Full (c3fb91a9)

[openjdk]

@asilichenko Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

[openjdk]

⚠️ @asilichenko This pull request contains merges that bring in commits not present in the target repository. Since this is not a "merge style" pull request, these changes will be squashed when this pull request in integrated. If this is your intention, then please ignore this message. If you want to preserve the commit structure, you must change the title of this pull request to Merge <project>:<branch> where <project> is the name of another project in the OpenJDK organization (for example Merge jdk:master).

[asilichenko]

@sormuras done

[sormuras]

Okay. Let's wait until a Reviewer also checks off this pull request. Next steps will be called out by the OpenJDK bot...

[openjdk]

⚠️ @asilichenko the full name on your profile does not match the author name in this pull requests' HEAD commit. If this pull request gets integrated then the author name from this pull requests' HEAD commit will be used for the resulting commit. If you wish to push a new commit with a different author name, then please run the following commands in a local repository of your personal fork:

$ git checkout fix-curl-error-options
$ git commit --author='Preferred Full Name <[email protected]>' --allow-empty -m 'Update full name'
$ git push

[asilichenko]

/integrate

[openjdk]

@asilichenko
Your change (at version 26d1921) is now ready to be sponsored by a Committer.

[sormuras]

/sponsor

[openjdk]

Going to push as commit 4544d5f.

[openjdk]

@sormuras @asilichenko Pushed as commit 4544d5f.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.