Fork ECF code into org.eclipse.equinox.p2.transport.native to eliminate external dependencies #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove the dependency on external Eclipse Communication Framework (ECF) bundles by forking their code directly into a new self-contained transport bundle.
Changes
Created
org.eclipse.equinox.p2.transport.nativebundle by copyingorg.eclipse.equinox.p2.transport.ecfecftonativeRequire-Bundledependencies onorg.eclipse.ecf,org.eclipse.ecf.filetransfer, andorg.eclipse.ecf.provider.filetransferInlined 207 Java files from ECF repository maintaining original
org.eclipse.ecf.*package structure:org.eclipse.ecfcore (77 files) - identity, events, security, containersorg.eclipse.ecf.identity(28 files) - ID system and namespacesorg.eclipse.ecf.filetransfer(65 files) - file transfer interfaces and service APIsorg.eclipse.ecf.provider.filetransfer(37 files) - URLConnection-based HTTP/HTTPS implementationUpdated MANIFEST.MF exports to expose inlined ECF packages with their original versions
Removed
P2SSLContextFactorywhich depended on externalorg.eclipse.ecf.core.security.SSLContextFactoryinterfaceArchitecture
The bundle now contains the full ECF file transfer stack:
Next Steps
Activatorto directly instantiate adapters instead of OSGi ServiceTracker lookupsWarning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
repo.eclipse.org/usr/lib/jvm/temurin-21-jdk-amd64/bin/java /usr/lib/jvm/temurin-21-jdk-amd64/bin/java --enable-native-access=ALL-UNNAMED -XX:+PrintFlagsFinal -Xmx2g -classpath /usr/share/apache-maven-3.9.11/boot/plexus-classworlds-2.9.0.jar -Dclassworlds.conf=/usr/share/apache-maven-3.9.11/bin/m2.conf -Dmaven.home=/usr/share/apache-maven-3.9.11 -Dlibrary.jansi.path=/usr/share/apache-maven-3.9.11/lib/jansi-native -Dmaven.multiModuleProjectDirectory=/home/REDACTED/work/p2/p2 org.codehaus.plexus.classworlds.launcher.Launcher clean compile -DskipTests(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.