Build OpenJ9 Windows jdk19+ with VS2022, and disable ccache

[pshipton]

OpenJ9 was missing the change to disable ccache for all versions.

Issue eclipse-openj9/openj9#16701

[pshipton]

@AdamBrousseau fyi

[karianna]

In /github/workspace/build-farm/platform-specific-configurations/windows.sh line 227:
fi
^-- SC1089 (error): Parsing stopped here. Is this keyword correctly matched up?

[pshipton]

Oops, fixed now.

[karianna]

OK the Alpine build is failing because it is merging/generating a file that has a merge conflict: <<<<<<< HEAD

No idea where this is coming from as a GitHub code search indicates that's nowhere in the entire Adoptium org.

[sxa]

Does --disable-ccache do anything on Windows JDK builds? I didn't think it was possible to use it there.

[pshipton]

Does --disable-ccache do anything on Windows JDK builds? I didn't think it was possible to use it there.

I don't know, I'm just making it consistent. 32-bit builds use it, non-openj9 builds use it, and openj9 jdk8 64-bit uses it. My change uses it for openj9 64-bit builds of all versions.

[sxa]

@karianna Are you happy with this now after Peter addressed your request?

[karianna]

OK the Alpine build is failing because it is merging/generating a file that has a merge conflict: <<<<<<< HEAD

No idea where this is coming from as a GitHub code search indicates that's nowhere in the entire Adoptium org.

The Alpine build still seems to have a merge conflict?

[gdams]

I think we should try and align hotspot/openj9 better here. @sxa I think we were talking about bumping the Temurin builds to VS 2022 as well?

[github-actions]

A block has been put on this Pull Request as this repository is temporarily under a code freeze due to an ongoing release cycle.

If this pull request needs to be merged during the release cycle then please comment /merge and a PMC member will be able to remove the block.

If the code freeze is over you can remove this block by commenting /thaw.

[sxa]

OK the Alpine build is failing because it is merging/generating a file that has a merge conflict: <<<<<<< HEAD
No idea where this is coming from as a GitHub code search indicates that's nowhere in the entire Adoptium org.

The Alpine build still seems to have a merge conflict?

That's the separate branch that MSFT is maintaining I believe - @gdams can you check this one?

[sxa]

I think we should try and align hotspot/openj9 better here. @sxa I think we were talking about bumping the Temurin builds to VS 2022 as well?

Possibly but we can do that under a separate PR if desired. At the moment all the work that is being done to enable reproducibility for Temurin is on VS2019 and additional work would be required to move it up.

[AdamBrousseau]

Can this be merged?

[karianna]

I think we're still in release freeze.

[sxa]

/thaw

Pull Request unblocked - code freeze is over.