Add capability and requirement for org.eclipse.equinox.internal.p2.repository.Transport#972
Add capability and requirement for org.eclipse.equinox.internal.p2.repository.Transport#972trancexpress wants to merge 1 commit intoeclipse-equinox:masterfrom
Conversation
…pository.Transport Fixes: eclipse-equinox#971
|
I can run the test fine with the 2 changes here. |
|
Fail on Linux is: Looks like the transport bundle requires the repository bundle, which needs the service: |
|
@trancexpress I'll need to look into this I think it is a general Tycho problem and we likely want a generic solution for this as we have for |
|
@trancexpress as the Eclipse is now in RC1 phase and I want to publish a Tycho release soon I would like to postpone this (and the Tycho change) to the next release I assume this is not critical here as one can always manually add the required dependency. |
|
Sure, no rush here. |
| org.eclipse.core.jobs;bundle-version="3.5.100" | ||
| Service-Component: OSGI-INF/ecfTransport.xml, | ||
| OSGI-INF/org.eclipse.equinox.internal.p2.transport.ecf.P2SSLContextFactory.xml | ||
| Provide-Capability: osgi.implementation;p2.agent.servicename=org.eclipse.equinox.internal.p2.repository.Transport;version=1.4.600 |
There was a problem hiding this comment.
This does not look correct, usually the namespace should match the filter see
Also I'm not sure if implementation is a good choice, if we look at how P2 implements this, the osgi service namespace seems a better fit (and we can automate this in the future hopefully to not write these on our own):
So what we do here is providing an IAgentService with the given property and I would say it must be
osgi.service;objectClass:List<String>="org.eclipse.equinox.p2.core.spi.IAgentServiceFactory";p2.agent.servicename="org.eclipse.equinox.internal.p2.repository.Transport"
@tjwatson can you verify? Sadly the OSGi spec is a bit short on this with examples :-\
Fixes: #971