You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (Jira)" <ji...@apache.org> on 2020/03/19 10:35:00 UTC

[jira] [Closed] (SLING-9186) Use provide/require capability for the repoinit language version

     [ https://issues.apache.org/jira/browse/SLING-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz closed SLING-9186.
--------------------------------------

> Use provide/require capability for the repoinit language version
> ----------------------------------------------------------------
>
>                 Key: SLING-9186
>                 URL: https://issues.apache.org/jira/browse/SLING-9186
>             Project: Sling
>          Issue Type: Improvement
>          Components: Repoinit
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: Repoinit JCR 1.1.22, Repoinit Parser 1.5.2
>
>
> Changes to the repoinit.jcr module often require a new version of the language parser module, which can not always be expressed in terms of Java package versions.
> OSGi capabilities will allow us to avoid out-of-sync versions of these bundles, so my current plan is to add
> {code:java}
> Provide-Capability: org.apache.sling.repoinit.language;version:Version="8.0"
> {code}
> to the repoinit.parser bundle, with the corresponding {{Require-Capability}} in the jcr.repoinit bundle.
> Starting at arbitrary V8.0 of the repoinit language, I think eight is more than the number of important language changes we've had since this module started. And we can then increment the language version when new instructions or options are added.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)