This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 324352 - [metadata] p2 support for OSGi generic capabilities.
Summary: [metadata] p2 support for OSGi generic capabilities.
Status: CLOSED DUPLICATE of bug 313553
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks: 361877
  Show dependency tree
 
Reported: 2010-09-02 16:28 EDT by Thomas Watson CLA
Modified: 2016-04-13 01:48 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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 ***