[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Re: [p2-dev] who should declare dependencies on ds?
- From: Thomas Watson <tjwatson@xxxxxxxxxx>
- Date: Thu, 1 Apr 2010 12:50:49 -0500
- Delivered-to: email@example.com
Note that Equinox does have the ability to declare non-code dependencies in bundle manifests. See Eclipse-GenericCapability and Eclipse-GenericRequire headers at:
This could be used by the DS implementation to declare a DS runtime capability and bundles defining DS components could declare a requirement on the DS runtime capability. But this mechanism only describes resolve time dependencies. It still would not solve Jeff's other concerns about the need to have DS active in order to truly work. Also note that p2 meta-data currently does not reflect the generic capabilities/requirements declared in a bundle manifest so even if we specified these today I don't think it would really help in ensuring a DS runtime is provisioned by p2. Perhaps we should consider adding that to p2?
Also note that the OSGi alliance is currently looking at providing a standard way for declaring generic capabilities and requirements for a future core specification. We should keep an eye on this space and feed any additional requirements we may have to OSGi in this area.
Jeff McAffer ---04/01/2010 11:46:32 AM---It should be up to the system integrator. Actually, there should be metadata (in p2) that expresses the need for various servic
Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>
P2 developer discussions <p2-dev@xxxxxxxxxxx>
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
04/01/2010 11:46 AM
[equinox-dev] Re: [p2-dev] who should declare dependencies on ds?
It should be up to the system integrator. Actually, there should be metadata (in p2) that expresses the need for various services to be present to make the integrator's job easier but ultimately inclusion/activation/... are in the eye of the beholder. So we should not cod classpath (bundle or package) dependencies, rather we need more markup in p2 metadata to capture these non-classpath-related dependencies.
More detail: In this case you could declare a package dependency on the ds package but that will only get you the interfaces and not the implementation. The producer could similarly declare a bundle dependency on the Equinox ds bundle. This is short sighted as there are other DS implementations. Various p2 features could include the Equinox DS bundle. This is better but suffers from the same problem--that feature would not be usable with other DS implementations.
Note that the problem is a friend of the HTTP service, Help system and myriad of other situations where people need a service to be there but there is no clear declaration of that dependency.
Note also that simply having DS there is not enough. It needs to be started. This is a product/launch level concern (i.e., the DS bundle can/should not say that it should always be started).
So, unless the p2/ds problem is burning, it would be better to address the underlying issue than ad hoc addressing of the symptoms.
On 2010-04-01, at 12:21 PM, Susan Franklin McCourt wrote:
equinox-dev mailing list