Update tycho-build to 4.0.4

[akurtakov]

No description provided.

[github-actions]

Test Results

     24 files  ±0       24 suites  ±0   11m 26s ⏱️ +34s
2 150 tests ±0  2 105 ✔️ ±0  45 💤 ±0  0 ❌ ±0 
2 194 runs  ±0  2 149 ✔️ ±0  45 💤 ±0  0 ❌ ±0 

Results for commit e0900a2. ± Comparison against base commit 0582356.

[akurtakov]

@laeubi what's the status with the failing TCKs? Is anyone working on fixing them?

[laeubi]

Not sure if anyone in Eclipse WG / OSGi WG has demands of Equinox passing all official TCKs.... at least we must take care that we do not break more TCKs...

[laeubi]

e.g. Device Access Specification has failing test, no idea if anyone is actually using this, maybe we can drop it from equinox completely @tjwatson ?

[akurtakov]

Not sure if anyone in Eclipse WG / OSGi WG has demands of Equinox passing all official TCKs.... at least we must take care that we do not break more TCKs...

How will that be detected? Right now I simply ignore TCK verification results totally.

[laeubi]

You can see the results from master here:

https://github.com/eclipse-equinox/equinox#implemented-services-an-compliance

the you can compare with for example this:
https://github.com/eclipse-equinox/equinox/actions/runs/7030130135/job/19129880065

[akurtakov]

I have doubts that anyone will do the extra effort (me included).

[laeubi]

I have doubts that anyone will do the extra effort (me included).

As said it all depends on if we need Equinox to be something that implements something like OSGi or we need it to be an OSGi Specification compliant implementation ... A bit like JDT with Java 21...

[akurtakov]

My question here is from releng POV - as long as people get used to see the red cross they stop caring about verification builds at all.