Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 324352

Summary: [metadata] p2 support for OSGi generic capabilities.
Product: [Eclipse Project] Equinox Reporter: Thomas Watson <tjwatson>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: david_williams, pascal, petar.petrov, t-oberlies
Version: 3.7Keywords: helpwanted
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on:    
Bug Blocks: 361877    

Description Thomas Watson CLA 2010-09-02 16:28:19 EDT 
For OSGi R4.3 the RFC 154 is introducing meta-data for specifying generic capabilities and requirements.

See bug323427 and bug323964

We should add support to p2 to support these new types of constraints in OSGi.
Comment 1 Petar Petrov CLA 2011-11-18 03:13:21 EST 
Bug360659 is a real-world usecase of things gone wrong because of missing metadata.
Comment 2 Tobias Oberlies CLA 2012-08-31 12:23:10 EDT 
Isn't the p2 metadata model powerful enough to represent OSGi generic capabilities? AFAIK, this is just a matter of publishing the new manifest headers, and this is tracked as bug 313553. 

Bug 360659 is an orthogonal problem AFAIK: p2 doesn't support mandatory attributes, and these could be in fact be difficult to encode with the current metadata model.

Proposing to close as duplicate of bug 313553.
Comment 3 Thomas Watson CLA 2012-09-04 08:29:50 EDT 
(In reply to comment #2)
> Isn't the p2 metadata model powerful enough to represent OSGi generic
> capabilities? AFAIK, this is just a matter of publishing the new manifest
> headers, and this is tracked as bug 313553. 

Yes, I think this should be possible.

> 
> Bug 360659 is an orthogonal problem AFAIK: p2 doesn't support mandatory
> attributes, and these could be in fact be difficult to encode with the
> current metadata model.

I agree.

> 
> Proposing to close as duplicate of bug 313553.

OK with me.

*** This bug has been marked as a duplicate of bug 313553 ***