[
https://issues.apache.org/jira/browse/SLING-9186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-9186.
----------------------------------------
Resolution: Fixed
The {{org.apache.sling.repoinit.language}} OSGi capability is now provided by
https://github.com/apache/sling-org-apache-sling-repoinit-parser/ and required
by https://github.com/apache/sling-org-apache-sling-jcr-repoinit with a
specific version number.
> 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.4.4
>
>
> 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)
