[
https://issues.apache.org/jira/browse/SLING-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309237#comment-14309237
]
Felix Meschberger edited comment on SLING-4358 at 2/6/15 2:49 PM:
------------------------------------------------------------------
What RFC would that be ? [Contracts RFC
180|https://github.com/osgi/design/blob/master/rfcs/rfc0180/rfc-0180-portable-java-contracts.pdf?raw=true]
?
So we would probably have:
{code}
Provide-Capability: osgi.contract;
osgi.contract=AdobeSightly;
version:Version=1.1
{code}
We don't have a uses clause because the spec does not define a Java API.
was (Author: fmeschbe):
What RFC would that be ? Contracts RFC 180 ?
So we would probably have:
{code}
Provide-Capability: osgi.contract;
osgi.contract=AdobeSightly;
version:Version=1.1
{code}
We don't have a uses clause because the spec does not define a Java API.
> Add the 'Provide-Capability' OSGi header to the
> org.apache.sling.scripting.sightly bundle
> -----------------------------------------------------------------------------------------
>
> Key: SLING-4358
> URL: https://issues.apache.org/jira/browse/SLING-4358
> Project: Sling
> Issue Type: Sub-task
> Components: Scripting
> Reporter: Radu Cotescu
> Fix For: Scripting Sightly Engine 1.0.0
>
>
> The OSGi {{Provide-Capability}} \[0\] header should be added to the
> {{org.apache.sling.scripting.sightly}} bundle to easily identify what version
> of the Sightly specification \[1\] the bundle implements.
> \[0\] - http://wiki.osgi.org/wiki/Provide-Capability
> \[1\] - https://github.com/Adobe-Marketing-Cloud/sightly-spec/releases
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
