[Build] Try run mavenBuild-workflow with CMD shell on Windows

[HannesWell]

Test if executing the build with CMD under Windows helps to fix the test failures:

• [Build] Run mavenBuild-workflow with CMD shell on Windows eclipse-platform/eclipse.platform.releng.aggregator#3042

[github-actions]

Test Results

  375 files  + 10    375 suites  +10   47m 1s ⏱️ + 1m 15s
1 905 tests ±  0  1 902 ✅ + 18  3 💤 ±0  0 ❌  - 18 
6 715 runs  +128  6 706 ✅ +143  9 💤 +3  0 ❌  - 18 

Results for commit ad34335. ± Comparison against base commit 086dd96.

[merks]

The failure looks like some cleanup that was not properly completed

21:51:41 Missing requirement: org.eclipse.sdk.tests.feature.group 4.36.0.qualifier requires 'org.eclipse.equinox.p2.iu; org.eclipse.jsch.tests 0.0.0' but it could not be found

it’s always a good plan to have and sdk workspace so you see everything when one deletes something. I suppose the I-build might fail too.

[HannesWell]

The failure looks like some cleanup that was not properly completed

Indeed. Should be fixed with

• Remove removed o.e.jsch.tests plugin from sdk.tests feature eclipse-platform/eclipse.platform.releng.aggregator#3043

[HannesWell]

This is not necessary anymore as it confirmed that the P2 build test failures are fixed with

• [Build] Run mavenBuild-workflow with CMD shell on Windows eclipse-platform/eclipse.platform.releng.aggregator#3042

Thank you for the hint!