Updating ICU jar

  1. On the ICU4J side, identify the release to be used. Note that a release (including pre-release) is needed, not simply a tag.
    1. If the ICU4J version you want has already been released, you will use that one and no action is needed on the ICU4J side.
      1. Example: "release-68-1" or "release-69-rc"
    2. Otherwise, you will need to create an ICU4J pre-release with a snapshot:
      1. Example: cldr/2021-03-09 - note the "cldr/" and the date.
      2. Create the release as a pre-release (checkbox in GitHub: "X This is a pre-release")
  2. Next, verify that the package has been created.
    1. This is created by a GitHub action on the ICU4J side. It will take some time once 
    2. Click the package link to browse packages.
    3. You should see a package created with a version in one of the following forms:
      1.  <version>69.1-SNAPSHOT-release-69-rc</version>
      2.  <version>69.1-cldr-2020-03-09</version>
  3. Finally, create the PR.
    1. Here is an example PR: https://github.com/unicode-org/cldr/pull/1121
    2. The PR needs to be against the correct branch, etc.
    3. The only change is to update tools/pom.xml to update the icu4j.version variable to match the <version> from ICU in step 2 above, for example: <icu4j.version>69.1-SNAPSHOT-release-69-rc</icu4j.version> 
    4. Note: This is usually a simple enough fix that the PR can be done through the GitHub web interface by clicking "edit" on pom.xml.
    5. The test can be run locally with "mvn package". See Maven Setup.
    6. Make sure the PR builds successfully, and merge it after appropriate review.