Fix release version for 1.2.0

[chanseokoh]

Fixes #2026.

[codecov-io]

Codecov Report

Merging #2027 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2027   +/-   ##
=========================================
  Coverage     66.06%   66.06%           
  Complexity     1864     1864           
=========================================
  Files           322      322           
  Lines         12534    12534           
  Branches       1137     1137           
=========================================
  Hits           8281     8281           
  Misses         3828     3828           
  Partials        425      425

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9359fca...1a99a22. Read the comment docs.

[briandealwis]

Hmm, the category still isn't appearing. Investigating.

[elharo]

Where/what exactly are you not seeing?

[chanseokoh]

@briandealwis try re-installing. I see 1.2.0.

[briandealwis]

Huh, in my local build, the category IU isn't copied across into the target repository. That is:

$ unzip -p gcp-repo/target/repository/content.jar | grep "<unit.*id='com.google.cloud.tools.eclipse.category'"

is empty unless I change the requires.1.range to a tight bound.

I don't know why it's working in the main builds.

Anyways, I have a patch that will pull the version from the pom.xml so that we don't have to modify the p2.inf for future releases.

[briandealwis]

Ah, it works in the release build as release/release_after_kokoro.sh re-publishes the signed features and bundles, and then re-publishes the metadata.product (which pulls in the metadata.p2.inf).

[elharo]

So, no need to hold this release, right?

[briandealwis]

Good to go 👍