This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 211611 - Use Require/Provided-Capabilities for NetBeansInOSGi
Summary: Use Require/Provided-Capabilities for NetBeansInOSGi
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Netigso (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks: 210325
  Show dependency tree
 
Reported: 2012-04-23 23:09 UTC by Jesse Glick
Modified: 2014-05-26 05:08 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

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 Jesse Glick 2012-04-23 23:09:09 UTC 
Splitting this off from bug #210325 since it does not seem necessary for 7.2.
Comment 1 Jesse Glick 2012-04-24 12:59:59 UTC 
My original assumption was that NB tokens would map directly to capability names with no qualifications:

OpenIDE-Module-Provides: some.Interface
OpenIDE-Module-Requires: another.Interface

=>

Provide-Capability: some.Interface
Require-Capability: another.Interface

Yarda however suggested another idiom:

"For our purposes we could probably define org.netbeans.token
capability. With attribute token and use it like:

OpenIDE-Module-Provides: xyz

Provide-Capability: org.netbeans.token;token:String=xyz

for providing. And for requiring, needing or recommending:

Require-Capability: org.netbeans.token;resolve:=mandatory/optional;
  filter:=(token=xyz);effective:=startup"

Not sure if the more complex idiom offers some advantages.
Comment 2 Jaroslav Tulach 2014-05-26 05:08:29 UTC 
No plans to work on this any time soon.