Force qualifier updates

[merks]

eclipse-platform/eclipse.platform.releng.aggregator#3011

[merks]

@iloveeclipse @akurtakov

Is it okay to force all fragments and the host? It seems to me these all always have the same qualifier in the repository:

[github-actions]

Test Results

   539 files  ±0     539 suites  ±0   27m 50s ⏱️ - 1m 12s
 4 337 tests ±0   4 321 ✅ +1   15 💤 ±0  1 ❌  - 1 
16 601 runs  ±0  16 463 ✅ +1  137 💤 ±0  1 ❌  - 1 

For more details on these failures, see this check.

Results for commit e89a3ae. ± Comparison against base commit 8efc599.

[merks]

@iloveeclipse @akurtakov @MohananRahul

The build failures are unrelated. Note that once I complete the Orbit milestone build and contribute it to the Platform's TP, I will merge this PR if there is no feedback in the meantime.

[akurtakov]

I was AFK . Forcing them all wouldn't hurt.

[akurtakov]

Merging as the test failure is unstable windows test.

[HannesWell]

Is it okay to force all fragments and the host? It seems to me these all always have the same qualifier in the repository:

Yes the native fragments always have the same qualifier as their host and it's sufficient to only touch the latter, due to:

eclipse.platform.swt/binaries/pom.xml

Line 78 in 5c5eae1

<timestampProvider>fragment-host</timestampProvider>

which was configured via

• Use the new fragment-host timestamp provider #1096

[merks]

I see. So for future reference, no SWT native fragment ever needs to be qualifier forced, only the host might need to be qualifier forced. Thanks.