Skip to content

Avoid ECF dependency#989

Draft
merks wants to merge 1 commit into
eclipse-mylyn:mainfrom
merks:pr-no-ecf
Draft

Avoid ECF dependency#989
merks wants to merge 1 commit into
eclipse-mylyn:mainfrom
merks:pr-no-ecf

Conversation

@merks

@merks merks commented Dec 13, 2025

Copy link
Copy Markdown
Contributor
  • Remove the one use of ECF for what is essentially "just a configuration convince" in what I believe to be rare instances where servers might be discoverable on the network.

- Remove the one use of ECF for what is essentially "just a
configuration convince" in what I believe to be rare instances where
servers might be discoverable on the network.
@github-actions

Copy link
Copy Markdown

Test Results

 1 536 files  ±0   1 536 suites  ±0   11m 37s ⏱️ +11s
 4 774 tests ±0   4 719 ✅ ±0   55 💤 ±0  0 ❌ ±0 
14 334 runs   - 2  14 169 ✅  - 2  165 💤 ±0  0 ❌ ±0 

Results for commit 2c89c20. ± Comparison against base commit 2261181.

@ruspl-afed

Copy link
Copy Markdown
Contributor

Mylyn has a lot of use cases that may be considered "rare". What is so special regarding ECF @merks ?

@merks

merks commented Dec 13, 2025

Copy link
Copy Markdown
Contributor Author

It's a bit of a proof of concept that might one day become urgent...


I don't wish to create a biased assessment, but the way I see it, there are a number of problems with ECF:

  • ECF does not reliably produce releases.
  • ECF does not reliably merge pull requests.
  • ECF does does not accept help, but suffers from severe resource constraints.
  • ECF is no longer able to release to maven central (and does not accept help with that).
  • ECF does not reliably participate in SimRel.

As such, the Platform and Oomph unfortunately need to start considering alternatives to the growing risks of a stalemate in this core communication layer.

As a recent example, we needed to create P2SSLContextFactory as a workaround for a problem in ECF implementation:

http://github.com/eclipse-equinox/p2/pull/968

That problem remains today. There appears to be little hopeful that this will change.

As such, I see growing risk with little hope. And, even if we find an alternative solution (which could include an alternative discovery implementation, but that's yet more work, including testing which is difficult because p2 and Oomph do not use this) we might well end up in a situation where all the EPP packages include Mylyn and transitively include ECF without the P2SSLContextFactory workaround continuing to cause problems.

@merks merks marked this pull request as draft December 13, 2025 08:55
@ruspl-afed

Copy link
Copy Markdown
Contributor

Thank you for sharing your concerns @merks
It is a pity that such a rich framework like ECF has come to such a state.

I agree with you proposal that reduces the surface of potential risk.

Comment thread org.eclipse.mylyn-target/org.eclipse.mylyn.baseline.target
@merks

merks commented Dec 13, 2025

Copy link
Copy Markdown
Contributor Author

Yes, it's definitely pity. I have tried to help keep things on track.

We can leave this is PR in a draft state until such a time that we are forced to take some type of remedial action...

@ruspl-afed ruspl-afed left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants