scottslewis
commented
6 months ago Hi Ed.
I'm really not sure the best path and strategy for moving forward to updating the ECF's 3rd party dependencies. Currently ECF's target platform relies on bundles from old Orbit versions, even in cases where there are newer bundles available in the latest Orbit builds, e.g., json versus org.json.
* https://repo1.maven.org/maven2/org/json/json/20230227/This target platform is current being used, at least by default:
The following are things that could be pulled into a newer Orbit build
* https://repo1.maven.org/maven2/commons-httpclient/commons-httpclient/3.1 - This is ancient and is not updated beyond 2007. It's a problem waiting to happen. * https://repo1.maven.org/maven2/org/apache/httpcomponents/httpclient-win/4.5.14/ - This should have been updated from 4.5.13 but that never happened. * https://repo1.maven.org/maven2/rome/rome/0.9 or https://repo1.maven.org/maven2/rome/rome/1.0 - This is for com.sun.syndication which also appears to have gone dormant in 2010. This looks like a problem waiting to happen.
Hi @merks
I will take a look at the dependencies above and determine whether to remove and/or deprecate the depending test code and/or old filetransfer or other providers.
* https://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/3.9.2 - This looks very much alive, but the latest breaks APIs. Also, it seem so drag in everything but the kitchen sink. I could spend days trying to determine which dependencies are optional or not
The zookeeper discovery provider was originally created by Wim Jongman aka @wimjongman . I've sent an email to Wim and ecf-dev mailing list asking that Wim let me/us know if something other than just deprecating this provider and removing the old third party dependencies should be done.
* https://repo1.maven.org/maven2/dnsjava/dnsjava/3.5.3 - This looks pretty lively. The latest breaks APIs. Added to Orbit:
The dnssd discovery provider was created by Markus Kuppe aka @lemmy. The same ecf-dev email was sent to Markus also and hopefully he will respond on ecf-dev, to me directly, or even here about what should be done with dnssd provider and the dnsjava dependency.
lemmy
merks
wimjongman
I'm really not sure the best path and strategy for moving forward to updating the ECF's 3rd party dependencies. Currently ECF's target platform relies on bundles from old Orbit versions, even in cases where there are newer bundles available in the latest Orbit builds, e.g., json versus org.json.
This target platform is current being used, at least by default:
https://github.com/eclipse/ecf/blob/28753b9b4da377be0b51d273428ba4193fec44c8/releng/org.eclipse.ecf.releng.target/ecf-2022-03.target#L40-L69
The following are things that could be pulled into a newer Orbit build
I've been prototyping creating new Orbit versions for the above and using them in ECF:
But it feels like a bit of an uphill battle and I'm not sure if the project is actually going to update to new content from Orbit. The zookeeper in particular looks like a big can of works.
@scottslewis
I would be good to understand the expectations around this topic. ECF does contribute a significant amount of content to SimRel and that is currently dragging in some really old content. I can certainly understand if you (or the project) have other priorities, in which case it doesn't make so much sense for me to invest significant time in providing things in Orbit that won't actually be consumed and redistributed by ECF.